Skip to content

Commit 8403fbf

Browse files
b-Tomasb-Tomas
committed
Git renormalize
1 parent 1e46d4e commit 8403fbf

12 files changed

Lines changed: 3392 additions & 3391 deletions

File tree

‎.gitattributes‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
* text=auto eol=lf

‎.pypirc‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
index-servers =
2-
pypi
3-
4-
[pypi]
5-
repository: https://upload.pypi.org/legacy/
6-
username: __token__
1+
index-servers =
2+
pypi
3+
4+
[pypi]
5+
repository: https://upload.pypi.org/legacy/
6+
username: __token__

‎CODE_OF_CONDUCT.md‎

Lines changed: 79 additions & 79 deletions
Original file line numberDiff line numberDiff line change
@@ -1,79 +1,79 @@
1-
<!--
2-
SPDX-FileCopyrightText: 2025 InOrbit, Inc.
3-
4-
SPDX-License-Identifier: MIT
5-
-->
6-
7-
# Contributor Covenant Code of Conduct
8-
9-
## Our Pledge
10-
11-
In the interest of fostering an open and welcoming environment, we as
12-
contributors and maintainers pledge to make participation in our project and
13-
our community a harassment-free experience for everyone, regardless of age, body
14-
size, disability, ethnicity, sex characteristics, gender identity and expression,
15-
level of experience, education, socioeconomic status, nationality, personal
16-
appearance, race, religion, or sexual identity and orientation.
17-
18-
## Our Standards
19-
20-
Examples of behavior that contributes to creating a positive environment
21-
include:
22-
23-
* Using welcoming and inclusive language
24-
* Being respectful of differing viewpoints and experiences
25-
* Gracefully accepting constructive criticism
26-
* Focusing on what is best for the community
27-
* Showing empathy towards other community members
28-
29-
Examples of unacceptable behavior by participants include:
30-
31-
* The use of sexualized language or imagery and unwelcome sexual attention or
32-
advances
33-
* Trolling, insulting/derogatory comments, and personal or political attacks
34-
* Public or private harassment
35-
* Publishing others' private information, such as a physical or electronic
36-
address, without explicit permission
37-
* Another conduct that could reasonably be considered inappropriate in a
38-
professional setting
39-
40-
## Our Responsibilities
41-
42-
Project maintainers are responsible for clarifying the standards of acceptable
43-
behavior and are expected to take appropriate and fair corrective action in
44-
response to any instances of unacceptable behavior.
45-
46-
Project maintainers have the right and responsibility to remove, edit, or
47-
reject comments, commits, code, wiki edits, issues, and other contributions
48-
that are not aligned to this Code of Conduct, or to ban temporarily or
49-
permanently any contributor for other behaviors that they deem inappropriate,
50-
threatening, offensive, or harmful.
51-
52-
## Scope
53-
54-
This Code of Conduct applies both within project spaces and in public spaces
55-
when an individual is representing the project or its community. Examples of
56-
representing a project or community include using an official project e-mail
57-
address, posting via an official social media account, or acting as an appointed
58-
representative at an online or offline event. Representation of a project may be
59-
further defined and clarified by project maintainers.
60-
61-
## Enforcement
62-
63-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
64-
reported by contacting the maintainers of this project, and we will
65-
attempt to resolve the issues with respect and dignity.
66-
67-
Project maintainers who do not follow or enforce the Code of Conduct in good
68-
faith may face temporary or permanent repercussions as determined by other
69-
members of the project's leadership.
70-
71-
## Attribution
72-
73-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
74-
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
75-
76-
[homepage]: https://www.contributor-covenant.org
77-
78-
For answers to common questions about this code of conduct, see
79-
https://www.contributor-covenant.org/faq
1+
<!--
2+
SPDX-FileCopyrightText: 2025 InOrbit, Inc.
3+
4+
SPDX-License-Identifier: MIT
5+
-->
6+
7+
# Contributor Covenant Code of Conduct
8+
9+
## Our Pledge
10+
11+
In the interest of fostering an open and welcoming environment, we as
12+
contributors and maintainers pledge to make participation in our project and
13+
our community a harassment-free experience for everyone, regardless of age, body
14+
size, disability, ethnicity, sex characteristics, gender identity and expression,
15+
level of experience, education, socioeconomic status, nationality, personal
16+
appearance, race, religion, or sexual identity and orientation.
17+
18+
## Our Standards
19+
20+
Examples of behavior that contributes to creating a positive environment
21+
include:
22+
23+
* Using welcoming and inclusive language
24+
* Being respectful of differing viewpoints and experiences
25+
* Gracefully accepting constructive criticism
26+
* Focusing on what is best for the community
27+
* Showing empathy towards other community members
28+
29+
Examples of unacceptable behavior by participants include:
30+
31+
* The use of sexualized language or imagery and unwelcome sexual attention or
32+
advances
33+
* Trolling, insulting/derogatory comments, and personal or political attacks
34+
* Public or private harassment
35+
* Publishing others' private information, such as a physical or electronic
36+
address, without explicit permission
37+
* Another conduct that could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Our Responsibilities
41+
42+
Project maintainers are responsible for clarifying the standards of acceptable
43+
behavior and are expected to take appropriate and fair corrective action in
44+
response to any instances of unacceptable behavior.
45+
46+
Project maintainers have the right and responsibility to remove, edit, or
47+
reject comments, commits, code, wiki edits, issues, and other contributions
48+
that are not aligned to this Code of Conduct, or to ban temporarily or
49+
permanently any contributor for other behaviors that they deem inappropriate,
50+
threatening, offensive, or harmful.
51+
52+
## Scope
53+
54+
This Code of Conduct applies both within project spaces and in public spaces
55+
when an individual is representing the project or its community. Examples of
56+
representing a project or community include using an official project e-mail
57+
address, posting via an official social media account, or acting as an appointed
58+
representative at an online or offline event. Representation of a project may be
59+
further defined and clarified by project maintainers.
60+
61+
## Enforcement
62+
63+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
64+
reported by contacting the maintainers of this project, and we will
65+
attempt to resolve the issues with respect and dignity.
66+
67+
Project maintainers who do not follow or enforce the Code of Conduct in good
68+
faith may face temporary or permanent repercussions as determined by other
69+
members of the project's leadership.
70+
71+
## Attribution
72+
73+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
74+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
75+
76+
[homepage]: https://www.contributor-covenant.org
77+
78+
For answers to common questions about this code of conduct, see
79+
https://www.contributor-covenant.org/faq

‎examples/example.fleet.yaml‎

Lines changed: 52 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,52 +1,52 @@
1-
# SPDX-FileCopyrightText: 2025 InOrbit, Inc.
2-
#
3-
# SPDX-License-Identifier: MIT
4-
5-
# The timezone of the robot location as a pytz timezone (https://pythonhosted.org/pytz/#helpers)
6-
location_tz: America/Los_Angeles
7-
# Logging configuration
8-
logging:
9-
# Connector log level (optional, can be set in the logging_config file) (DEBUG, INFO, WARNING, ERROR, CRITICAL)
10-
# Comment out to use the log level set in the logging_config file
11-
log_level: INFO
12-
# Logging configuration file (optional). Comment out to use the default configuration file
13-
config_file: ./logging.example.conf
14-
# Variables the logs configuration file can use (optional)
15-
# defaults:
16-
# # When the default config file is in use, this sets the output log file
17-
# log_file: ./logs/my-example-robot.log
18-
# The type of connector
19-
connector_type: example_bot
20-
# Update rate of the connector's main execution loop in Hz
21-
update_freq: 1.0
22-
# The ID of the InOrbit account that owns the robots (optional, required for use of footprints)
23-
account_id: my_inorbit_account
24-
# Robot key for InOrbit Connect robots (optional, delete if unused)
25-
# See https://api.inorbit.ai/docs/index.html#operation/generateRobotKey
26-
inorbit_robot_key:
27-
# Map configuration (optional)
28-
maps:
29-
frameIdA:
30-
file: ./example_map.png
31-
map_id: mapA
32-
map_label: Building A - Floor 1
33-
origin_x: 0.0
34-
origin_y: 0.0
35-
resolution: 0.05
36-
# User scripts directory (optional)
37-
user_scripts_dir: ./
38-
# Extra environment variables, useful for running user scripts (optional)
39-
env_vars:
40-
MY_ENV_VAR: my_value
41-
42-
# This is where you define custom fields specific to your robot's connector
43-
connector_config:
44-
example_bot_api_version: v1
45-
example_bot_hw_rev: v3
46-
example_bot_custom_value: test123
47-
48-
# Fleet configuration - contains robot-specific data
49-
fleet:
50-
- robot_id: fleet-robot-1
51-
- robot_id: fleet-robot-2
52-
- robot_id: fleet-robot-3
1+
# SPDX-FileCopyrightText: 2025 InOrbit, Inc.
2+
#
3+
# SPDX-License-Identifier: MIT
4+
5+
# The timezone of the robot location as a pytz timezone (https://pythonhosted.org/pytz/#helpers)
6+
location_tz: America/Los_Angeles
7+
# Logging configuration
8+
logging:
9+
# Connector log level (optional, can be set in the logging_config file) (DEBUG, INFO, WARNING, ERROR, CRITICAL)
10+
# Comment out to use the log level set in the logging_config file
11+
log_level: INFO
12+
# Logging configuration file (optional). Comment out to use the default configuration file
13+
config_file: ./logging.example.conf
14+
# Variables the logs configuration file can use (optional)
15+
# defaults:
16+
# # When the default config file is in use, this sets the output log file
17+
# log_file: ./logs/my-example-robot.log
18+
# The type of connector
19+
connector_type: example_bot
20+
# Update rate of the connector's main execution loop in Hz
21+
update_freq: 1.0
22+
# The ID of the InOrbit account that owns the robots (optional, required for use of footprints)
23+
account_id: my_inorbit_account
24+
# Robot key for InOrbit Connect robots (optional, delete if unused)
25+
# See https://api.inorbit.ai/docs/index.html#operation/generateRobotKey
26+
inorbit_robot_key:
27+
# Map configuration (optional)
28+
maps:
29+
frameIdA:
30+
file: ./example_map.png
31+
map_id: mapA
32+
map_label: Building A - Floor 1
33+
origin_x: 0.0
34+
origin_y: 0.0
35+
resolution: 0.05
36+
# User scripts directory (optional)
37+
user_scripts_dir: ./
38+
# Extra environment variables, useful for running user scripts (optional)
39+
env_vars:
40+
MY_ENV_VAR: my_value
41+
42+
# This is where you define custom fields specific to your robot's connector
43+
connector_config:
44+
example_bot_api_version: v1
45+
example_bot_hw_rev: v3
46+
example_bot_custom_value: test123
47+
48+
# Fleet configuration - contains robot-specific data
49+
fleet:
50+
- robot_id: fleet-robot-1
51+
- robot_id: fleet-robot-2
52+
- robot_id: fleet-robot-3

‎examples/example.yaml‎

Lines changed: 50 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,50 +1,50 @@
1-
# SPDX-FileCopyrightText: 2025 InOrbit, Inc.
2-
#
3-
# SPDX-License-Identifier: MIT
4-
5-
# The timezone of the robot location as a pytz timezone (https://pythonhosted.org/pytz/#helpers)
6-
location_tz: America/Los_Angeles
7-
# Logging configuration
8-
logging:
9-
# Connector log level (optional, can be set in the logging_config file) (DEBUG, INFO, WARNING, ERROR, CRITICAL)
10-
# Comment out to use the log level set in the logging_config file
11-
log_level: INFO
12-
# Logging configuration file (optional). Comment out to use the default configuration file
13-
config_file: ./logging.example.conf
14-
# Variables the logs configuration file can use (optional)
15-
# defaults:
16-
# # When the default config file is in use, this sets the output log file
17-
# log_file: ./logs/my-example-robot.log
18-
# The type of connector
19-
connector_type: example_bot
20-
# Update rate of the connector's main execution loop in Hz
21-
update_freq: 1.0
22-
# The ID of the InOrbit account that owns the robots (optional, required for use of footprints)
23-
account_id: my_inorbit_account
24-
# Robot key for InOrbit Connect robots (optional, delete if unused)
25-
# See https://api.inorbit.ai/docs/index.html#operation/generateRobotKey
26-
inorbit_robot_key:
27-
# Map configuration (optional)
28-
maps:
29-
frameIdA:
30-
file: ./example_map.png
31-
map_id: mapA
32-
map_label: Building A - Floor 1
33-
origin_x: 0.0
34-
origin_y: 0.0
35-
resolution: 0.05
36-
# User scripts directory (optional)
37-
user_scripts_dir: ./
38-
# Extra environment variables, useful for running user scripts (optional)
39-
env_vars:
40-
MY_ENV_VAR: my_value
41-
42-
# This is where you define custom fields specific to your robot's connector
43-
connector_config:
44-
example_bot_api_version: v1
45-
example_bot_hw_rev: v3
46-
example_bot_custom_value: test123
47-
48-
# Fleet configuration - contains robot-specific data
49-
fleet:
50-
- robot_id: my-example-robot
1+
# SPDX-FileCopyrightText: 2025 InOrbit, Inc.
2+
#
3+
# SPDX-License-Identifier: MIT
4+
5+
# The timezone of the robot location as a pytz timezone (https://pythonhosted.org/pytz/#helpers)
6+
location_tz: America/Los_Angeles
7+
# Logging configuration
8+
logging:
9+
# Connector log level (optional, can be set in the logging_config file) (DEBUG, INFO, WARNING, ERROR, CRITICAL)
10+
# Comment out to use the log level set in the logging_config file
11+
log_level: INFO
12+
# Logging configuration file (optional). Comment out to use the default configuration file
13+
config_file: ./logging.example.conf
14+
# Variables the logs configuration file can use (optional)
15+
# defaults:
16+
# # When the default config file is in use, this sets the output log file
17+
# log_file: ./logs/my-example-robot.log
18+
# The type of connector
19+
connector_type: example_bot
20+
# Update rate of the connector's main execution loop in Hz
21+
update_freq: 1.0
22+
# The ID of the InOrbit account that owns the robots (optional, required for use of footprints)
23+
account_id: my_inorbit_account
24+
# Robot key for InOrbit Connect robots (optional, delete if unused)
25+
# See https://api.inorbit.ai/docs/index.html#operation/generateRobotKey
26+
inorbit_robot_key:
27+
# Map configuration (optional)
28+
maps:
29+
frameIdA:
30+
file: ./example_map.png
31+
map_id: mapA
32+
map_label: Building A - Floor 1
33+
origin_x: 0.0
34+
origin_y: 0.0
35+
resolution: 0.05
36+
# User scripts directory (optional)
37+
user_scripts_dir: ./
38+
# Extra environment variables, useful for running user scripts (optional)
39+
env_vars:
40+
MY_ENV_VAR: my_value
41+
42+
# This is where you define custom fields specific to your robot's connector
43+
connector_config:
44+
example_bot_api_version: v1
45+
example_bot_hw_rev: v3
46+
example_bot_custom_value: test123
47+
48+
# Fleet configuration - contains robot-specific data
49+
fleet:
50+
- robot_id: my-example-robot

0 commit comments

Comments
 (0)