Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: handle multiple executors in WRROC entities #21

Open
Karanjot786 opened this issue Aug 21, 2024 · 0 comments
Open

feat: handle multiple executors in WRROC entities #21

Karanjot786 opened this issue Aug 21, 2024 · 0 comments
Assignees

Comments

@Karanjot786
Copy link
Member

Description

In the current implementation of the TESConverter, only the first executor is used when converting TES data to WRROC entities. However, a TES task can have multiple executors, which implies that the task consists of multiple steps.

Action Required

We need to determine how multiple executors should be handled when converting TES data to WRROC entities. The current approach of using only the first executor may not fully represent the task's complexity.

Proposed Solution

Consider the following options:

  1. Create Multiple WRROC Entries: Each executor could be converted into a separate WRROC entity.
  2. Aggregate Executors: Combine the information from all executors into a single WRROC entity, ensuring all steps are represented.
  3. Custom Handling: Develop a custom approach to represent multiple executors in WRROC entities.

This issue will be addressed in a future PR.

Impact

Properly handling multiple executors will ensure that the converted WRROC entities accurately represent the complexity of TES tasks.

Related Code

The current implementation can be found in TESConverter.convert_to_wrroc method.

References

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

No branches or pull requests

3 participants