Move to the benchmark folder to run one of the scripts.

If you have opend a benchmark, you should be able to execute ./run_instance 

The correct conditional ODE file location is given as a preset, such that you
just have to press enter when the following lines occur on the commandline. Note
that this is not necessary for the ISF 2016 benchmarks. 
    Enter name of conditional ODE XML file
    [condODEs.xml]
    
When a counterexample is found, you can decide to refine (enter 'r') or to
continue (enter 'c').
   What's next? (R)efine / (C)ontinue: r

This allows you to enter a set of location, conditional ode pairs.
However, if no refinement was specified, the analysis will abort.

To choose a location for refinement, enter the corresponding number.
    Choose a location to refine :
    1) on_1_in_control2_cycle
    2) off_1_in_control2_cycle
    
I.e. to refine location 'off_1_in_control2_cycle', enter '2'.

Choose a conditional ode analoguously. 
Note, that only those conditional odes whose condition intersects with the
invariant of the location and that have not yet been used to refine the location
are shown.

Afterwards, the refinement status of the chosen location is updated: 
    Location: off_1_in_control2_cycle
    1:[X], 2:[-], 3:[ ]
'1:[X]' indicates, that the first conditional ode is used for refinement
'2:[-]' indicates, that the second conditional ode is not allowed for refinement
'3:[ ]' indicates, that the third conditional ode is allowed for refinement, but
has not been applied so far
