Adding algorithms google form changes

[kvdblom]

Main questions

Number of Input variables (number(s) or range) *

• This should have some kind of indication about what we expect there. I.e., the maximum of the range should be a number where you still expect it to work reasonably well, or something to that effect.

Problem characteristics support

• This should indicate what supported means. I.e., does it mean 'it can run' or 'it is designed for this'. We've had this discussion, and even I am not sure what the outcome was...

Implementation

Requirements

• I think it would be clearer to also in this specific question again indicate that it concerns installation requirements of the implementation, e.g., packages, operating system, maybe hardware, ...

Additional information

Supported constraint types

• Should this have a 'None' option so we can distinguish between unknown and no constraint support?

Tags: Performance

• I wondered if this was perhaps more about the implementation than the algorithm itself. In my case it could be implemented in either way.

Other things

• I think I missed a field for a reference to a paper introducing the algorithm. That might be nice to include.

[Dvermetten]

Main questions

Number of Input variables (number(s) or range) *

• This should have some kind of indication about what we expect there. I.e., the maximum of the range should be a number where you still expect it to work reasonably well, or something to that effect.

I added this description: "Indicate either a fixed number, or a lower and upper bound for number of variables the submitted algorithm can reasonably expect to handle."

Problem characteristics support

• This should indicate what supported means. I.e., does it mean 'it can run' or 'it is designed for this'. We've had this discussion, and even I am not sure what the outcome was...

I added this "Describe what problem characteristics the algorithm can handle. Indicate supported if the algorithm can reasonably be expected to work in this scenario. Indicate 'Conditional' if a problem characteristic can only be supported only when some condition is met (e.g. a parameter has a non-default value). "

Implementation

Requirements

• I think it would be clearer to also in this specific question again indicate that it concerns installation requirements of the implementation, e.g., packages, operating system, maybe hardware, ...

Please list any requirements needed to install and run the implementation of the submitted algorithm (both software and hardware if relevant)

Additional information

Supported constraint types

• Should this have a 'None' option so we can distinguish between unknown and no constraint support?

I don't think so, that 'None' we can extract from the table in the section before this

Tags: Performance

• I wondered if this was perhaps more about the implementation than the algorithm itself. In my case it could be implemented in either way.

I mentioned now that you don't have to select something everywhere, only when it is relevant for the submitted method

Other things

• I think I missed a field for a reference to a paper introducing the algorithm. That might be nice to include.

Added

[kvdblom]

@Dvermetten One more thing I thought of: Maybe the "description" field should also have some (explicit) examples of what people might put there. E.g., full name of the algorithm (something I didn't think about when filling it out, but would probably be nice to add), other things not covered by the questions.

Other than this, it would probably be good if at least one more person test-drives the form.