Conversation
kvdblom
left a comment
There was a problem hiding this comment.
Some small changes / points for discussion
|
Status: I added the csv as an example, and added the other info as nested fields to other info in the yaml. I still need to remove non-empty fields, and check if suites already exist rather than just appending them again. That is for the next working meeting :) |
kvdblom
left a comment
There was a problem hiding this comment.
A few minor comments to resolve and/or turn into new issues. There are also some merge conflicts now, hopefully those are not too difficult to resolve...
There was a problem hiding this comment.
Rename to responses_OPL.csv to match the name csv_file = "responses_OPL.csv" in formresponse_to_yaml.py
(or the other way around)
| "Scientific motivation for the proposed suite / problem / generator" : "scientific motivation", | ||
| "Limitations of the proposed suite / problem / generator" : "limitations", | ||
| "Implemenation languages" : "implementation languages", | ||
| "Links to implementations" : "links to implementations", |
There was a problem hiding this comment.
Since we already have "Link to Implementation" :"implementation", above, should the two fields just be merged into one? (and maybe the second one removed from the google form, but that's another issue)
I think this may have originally been because the HTML page did not handle multiple links in one field, but I think we fixed that with #134
| variable type: Continuous | ||
| dimensionality: scalable' | ||
| objectives: 1 | ||
| constraints: Present |
There was a problem hiding this comment.
The Present / Not Present does not match the current problems.yaml/HTML page use of yes / no, making searching through them harder. This can be made into a new issue so we can merge this PR, but we should make sure not to forget.
Equivalent of csv_to_yaml, but with translation of the column names. Currently does no additional checking.