You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.data_groups
might be necessarydata_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 theflagmanager
task. Another option would be to make group name self-descriptive, but it would make the name too long.The text was updated successfully, but these errors were encountered: