New version of form-processing script for updated schema

[Dvermetten]

New (generated) script for converting the form responses (csv file) to the updated schema.

[Dvermetten]

Now adresses #186

[kvdblom]

Github action generate_html fails:

• when running uv run yaml_to_html.py, because problems.yaml contains '?' where input should be 'yes', 'no', 'some' or 'unknown'.
• Happens at least for: suite_morepo and suite_cec2015_dmoo
• Maybe these are ouput of the form processing script? Otherwise we can just change them to unknown and that should fix it

Github action check_new_problems fails:

• it cannot find module pydantic_yaml
• Maybe the problem is that: pydantic_yaml is in requirements.txt but not in utils/requirements.txt
• When running with uv run utils/validate_yaml.py problems.yaml (rather than python utils/validate_yaml.py problems.yaml as in the action), the action fails with ImportError: cannot import name 'default_columns' from 'yaml_to_html'

Execution of formresponse_to_yaml.py fails:

• When run with uv run formresponse_to_yaml.py, the error No such file or directory: 'responses_OPL.csv' comes up
• Suggestion: Change the default file name to the correct one
• Suggestion 2: Add instructions in a README (maybe in utils? Perhaps this entire script should go there?) on how thi should be executed.
• When run with uv run formresponse_to_yaml.py --csv OPL_form.csv execution fails with 44 validation errors -- Seemingly about execution times not being in the format expected by pydantic (but maybe not limited to that)

[kvdblom]

Merging main back in did no resolve any of these issues.

[Dvermetten]

Github action generate_html fails:

• when running uv run yaml_to_html.py, because problems.yaml contains '?' where input should be 'yes', 'no', 'some' or 'unknown'.
• Happens at least for: suite_morepo and suite_cec2015_dmoo
• Maybe these are ouput of the form processing script? Otherwise we can just change them to unknown and that should fix it

These are not from the processing, but I did change them to unknown anyway

Github action check_new_problems fails:

• it cannot find module pydantic_yaml
• Maybe the problem is that: pydantic_yaml is in requirements.txt but not in utils/requirements.txt
• When running with uv run utils/validate_yaml.py problems.yaml (rather than python utils/validate_yaml.py problems.yaml as in the action), the action fails with ImportError: cannot import name 'default_columns' from 'yaml_to_html'

I tried changing this to uv, but I think I overlooked something, will check this next week. The column naming this is fixed now

Execution of formresponse_to_yaml.py fails:

• When run with uv run formresponse_to_yaml.py, the error No such file or directory: 'responses_OPL.csv' comes up
• Suggestion: Change the default file name to the correct one
• Suggestion 2: Add instructions in a README (maybe in utils? Perhaps this entire script should go there?) on how thi should be executed.
• When run with uv run formresponse_to_yaml.py --csv OPL_form.csv execution fails with 44 validation errors -- Seemingly about execution times not being in the format expected by pydantic (but maybe not limited to that)

It seems I forgot to upload the readme last time, that is included now (should also fix the wrong default name for the csv). The validation errors remain an issue, I tried changing how the times are handled but either way I do it the validator complains:

If I make it a string:

impl_randoptgen.Implementation.evaluation_time
Input should be a valid set [type=set_type, input_value='milliseconds', >input_type=str]

If I make it a set:

gen_randoptgen.Implementation.evaluation_time.0
Input should be a valid string [type=string_type, input_value={'milliseconds'}, >input_type=set]

@olafmersmann Do you maybe know what I'm missing here?