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

Removing traces of Old Commondata #1974

Open
5 of 19 tasks
Radonirinaunimi opened this issue Mar 3, 2024 · 3 comments
Open
5 of 19 tasks

Removing traces of Old Commondata #1974

Radonirinaunimi opened this issue Mar 3, 2024 · 3 comments

Comments

@Radonirinaunimi
Copy link
Member

Radonirinaunimi commented Mar 3, 2024

Once #1678 and #1708 are merged, we should remove all the traces of the old commondata. This includes:

Once the process options module is finished

  • Remove all old commondata files for which a translation exists already.
  • Drop the mandatory status of the kinematic override key.
  • Stop using k1, k2, k3 inside validphys and allow for the dataframe of kinematics to be the complete information (don't drop the minmax)
  • relax the constraint that kinematic_coverage has to contain 3 variables

Once 4.1 is out

  • Remove all old commondata files (even if they have not been translated)
  • Remove the old commondata parser and old loader from validphys

(edit by @scarlehoff: added a hierarchy to the items and some extra ones)

@scarlehoff
Copy link
Member

@RoyStegeman @Radonirinaunimi

just to make sure that several of us don't end up working on the same stuff, if you want to tackle one of these issues either open an issue and assign yourself or put your name here in the list

in any case, next Wednesday I was planning to go through the list and assign tasks to everyone

@RoyStegeman
Copy link
Member

I assigned myself to updating the dataset names in the examples, so if I have time to work on any of these things, that's the one I'll address first.

@Radonirinaunimi
Copy link
Member Author

Radonirinaunimi commented Mar 8, 2024

I will assign myself starting from the first one on this list and the two issues #1940 and ...

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

3 participants