Skip to content

Preliminary HRI Challenge#680

Merged
CamilaTite26 merged 28 commits intomainfrom
hric
Mar 16, 2026
Merged

Preliminary HRI Challenge#680
CamilaTite26 merged 28 commits intomainfrom
hric

Conversation

@GilMM27
Copy link
Copy Markdown
Contributor

@GilMM27 GilMM27 commented Feb 24, 2026

  • Moved receptionist TM to misc/
  • Created new hric TM

@GilMM27 GilMM27 changed the title HRI Challenge Preliminary HRI Challenge Feb 25, 2026
@GilMM27 GilMM27 marked this pull request as ready for review February 25, 2026 03:39
@GilMM27 GilMM27 requested review from a team as code owners February 25, 2026 03:39
Copy link
Copy Markdown
Member

@Ale-Coeto Ale-Coeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LTGM.
For task manager testing we could make a list or document for different cases to make sure we cover all possible scenarios.
Also, just make sure to check merge conflicts

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is filename correct? hric.mmd

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, Human Robot Interaction Challenge (HRIC). Do you suggest another one?

self.subtask_manager.manipulation.move_to_position("front_low_stare")
self.subtask_manager.vision.follow_by_name(guest_1.name)
self.subtask_manager.hri.say(
f"Thanks for taking a seat {guest_2.name}. Allow me to introduce you to {guest_1.name}, they're favorite drink is {guest_1.drink}.",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be good to check if the names aren't default values. I think we can get penalized if we say wrong info, so it would be better to omit the names in such case.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch


for state, time_spent in sorted_states:
percentage = (time_spent / total_task_time) * 100
Logger.info(self, f"{state}: {time_spent:.2f}s ({percentage:.1f}%)")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could make our own Logger class and include functions to handle the timing report and other functionalities (very low priority, but could be useful in the future)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll create an issue on this

@JLDominguezM JLDominguezM requested a review from a team as a code owner March 1, 2026 00:38
@DanaeSG DanaeSG requested a review from a team as a code owner March 1, 2026 00:49
Comment thread task_manager/scripts/subtask_managers/manipulation_tasks.py
@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented Mar 9, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
18167028 Triggered Generic Password 7e67d00 .github/workflows/docker-publish.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@CamilaTite26 CamilaTite26 merged commit e34387a into main Mar 16, 2026
5 checks passed
@GerardoFJ GerardoFJ deleted the hric branch March 16, 2026 23:49
JLDominguezM added a commit that referenced this pull request Mar 18, 2026
* updated ask_and_confirm

* inverted logic operator

* replaced all receptionist mentions and started task manager

* added temporary todo

* finished preliminary implementation

* restored receptionist

* added diagram

* feat: added placae floor poses

* some bag manipulation

* Add hric.launch.py for motion planning and face tracking nodes

* Update run.sh to launch hric node for manipulation task

* change receptionist name vision

* change receptionist name vision

* change receptionist name vision

* some fixes + better take bag

* fixed follow face, ollama, and extract data

* refactor manipulation tasks to use 'pick_stare_at_table' position and improve retry logic for placing on sides

* fix pre-commit

* fix: update return values for path scanning to reflect execution status

* change constant name to hric

* use bool instead

---------

Co-authored-by: Hector Tovar <h.tovarm07@gmail.com>
Co-authored-by: JLDominguezM <A01285873@tec.mx>
Co-authored-by: Danaé <A00836760@tec.mx>
Co-authored-by: GerardoFJ <A00838645@tec.mx>
JLDominguezM added a commit that referenced this pull request Mar 21, 2026
* updated ask_and_confirm

* inverted logic operator

* replaced all receptionist mentions and started task manager

* added temporary todo

* finished preliminary implementation

* restored receptionist

* added diagram

* feat: added placae floor poses

* some bag manipulation

* Add hric.launch.py for motion planning and face tracking nodes

* Update run.sh to launch hric node for manipulation task

* change receptionist name vision

* change receptionist name vision

* change receptionist name vision

* some fixes + better take bag

* fixed follow face, ollama, and extract data

* refactor manipulation tasks to use 'pick_stare_at_table' position and improve retry logic for placing on sides

* fix pre-commit

* fix: update return values for path scanning to reflect execution status

* change constant name to hric

* use bool instead

---------

Co-authored-by: Hector Tovar <h.tovarm07@gmail.com>
Co-authored-by: JLDominguezM <A01285873@tec.mx>
Co-authored-by: Danaé <A00836760@tec.mx>
Co-authored-by: GerardoFJ <A00838645@tec.mx>
JLDominguezM added a commit that referenced this pull request Mar 24, 2026
* updated ask_and_confirm

* inverted logic operator

* replaced all receptionist mentions and started task manager

* added temporary todo

* finished preliminary implementation

* restored receptionist

* added diagram

* feat: added placae floor poses

* some bag manipulation

* Add hric.launch.py for motion planning and face tracking nodes

* Update run.sh to launch hric node for manipulation task

* change receptionist name vision

* change receptionist name vision

* change receptionist name vision

* some fixes + better take bag

* fixed follow face, ollama, and extract data

* refactor manipulation tasks to use 'pick_stare_at_table' position and improve retry logic for placing on sides

* fix pre-commit

* fix: update return values for path scanning to reflect execution status

* change constant name to hric

* use bool instead

---------

Co-authored-by: Hector Tovar <h.tovarm07@gmail.com>
Co-authored-by: JLDominguezM <A01285873@tec.mx>
Co-authored-by: Danaé <A00836760@tec.mx>
Co-authored-by: GerardoFJ <A00838645@tec.mx>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants