-
Notifications
You must be signed in to change notification settings - Fork 11
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
Remove the Proline runs (I did not upload the right ones) #228
Remove the Proline runs (I did not upload the right ones) #228
Comments
So you would delete if from the results repository? I think it would be good if we create a command to delete if from that json, so that formatting errors are avoided. This should be a simple deletion of a key in a dictionary. |
I just need the hash-codes of the datasets you would like to remove. Best pm them to me, as soon as the json is updated. |
that was my plan: to delete the corresponding lines. You make a good point, up to you: shall I delete or do you want to create the command? Not sure exactly how you would want to do that. Or option 3: I delete the 2 data sets for know and we work on a command for the next ones? |
I'll create a PR in 5mins... |
So dumping the json via pandas is different from the built-in json function per default. Can probably be fixed, but pandas as a dependency is not a big issue. |
OK, thanks! But I don't think that we should allow anyone to delete points, right? |
No, it's only in case there is a mistake. It's maintainer who can submit a PR to delete the points. @RobbinBouwmeester The repository is only for storage and only accessible to maintainers? |
The two proline points: Proline__20240122_190626 and Proline__20240122_190958 are not valid. I did not upload the correct ones. So I want to remove them from the set of public runs and here are my questions:
results.json
of the module repo: easy!Please let me know, I am happy to delete the lines in
results.json
as soon as you give me the green light. And then we will upload a lot more Proline runs with different parameters etc...The text was updated successfully, but these errors were encountered: