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

data_groups management #324

Open
tnakazato opened this issue Nov 25, 2024 · 1 comment
Open

data_groups management #324

tnakazato opened this issue Nov 25, 2024 · 1 comment

Comments

@tnakazato
Copy link
Contributor

I really like the concept of data_groups. I have a few considerations on it. I would appreciate it if you could consider them in the future development.

  • Maybe it's better to define reserved group name for common usecases such as "after applycal" or "ready for imaging"
  • Any mechanism to manage chronological evolution of data_groups might be necessary
  • There will be many versions of data_groups especially for data flagging. Now you have only group name to describe the group. But, as number of groups grows, users might need more detailed description on the data group. For example, they might need a field to store short description of the data group, just like the comment field in the flagmanager task. Another option would be to make group name self-descriptive, but it would make the name too long.
@Jan-Willem
Copy link
Member

  • We can suggest some standard names. However, I think it will be hard to come up with a comprehensive list now. As we develop our software we can define that list. This would not be a breaking change to XRADIO.
  • We can add date key.
  • We can add a description key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants