Closed kathrynroscoe closed 12 months ago
I have added the attributes results_dir (output\Scenarios\"Scnenario_name") to Scenario and DirectImpact classes and the results_dir (output\Scenarios\"Scnenario_name"\Flooding) to the Hazard class. SFINCS output is now written to the hazard.results_dir folder.
A note on the SFINCS simulation folder: HydroMT-SFINCS can only read the SFINCS netcdf results when it has a complete SFINCS folder. And hydromt-fiat is using hydromt-sfincs to read the sfincs results!!! So we should keep the SFINCS folder at least until FIAT is finished. If we need to read the SFINCS netcdf results again at a later stage, we could always recreate the sfincs folder again from the SFINCS template folder.
I am not deleting the SFINCS results yet. I am also running into the issue that there is a hydromt log file inside the folder, which is still in use when running a scenario and cannot be deleted.
@kathrynroscoe , what do you mean by the simulation folder is only created when the user wants them to be saved? We have to make at least temporary simulation folders somewhere. Do we delete them here if the user does not want to save them? Or shall we make temporary folder elsewhere and copy them here if the user wants to save them (that seems a little overcomplicated)
There was a mistake in the picture. The naming convention should be [filetype]_[scenario-name], but this was backwards for the risk return period flood maps. Here is a revised picture.
I moved the sfincs simulation folder
Kind of request
Changing existing functionality
Enhancement Description
The input and output folders would benefit from better organization from an end-user perspective.
Here is an overview of the proposed folder structure:
Task list
NOTE:
Use case
No response
Additional Context
No response