Chronix2Grid should generate chronix for different time resolution. It should not be hard coded like in "output_processor_to_chunks" from "output_processor.py".
A parameter to configure should exist for that, similarly to the "step_opf_min" parameter in params_opf.json.
A file "time_interval.info" should also be created as an output, containing only this time resolution (time between two timesteps) info in the format "%H:%M"
Be careful: 'dt' parameter might have a different meaning that the timestep resolution. dt is used for temporal correlation noise and could possibly be higher than the time_step resolution
Chronix2Grid should generate chronix for different time resolution. It should not be hard coded like in "output_processor_to_chunks" from "output_processor.py". A parameter to configure should exist for that, similarly to the "step_opf_min" parameter in params_opf.json. A file "time_interval.info" should also be created as an output, containing only this time resolution (time between two timesteps) info in the format "%H:%M"