ARTIST-Association / ARTIST-Association/ARTIST
scenario.h5 file saver for reconstructed models
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to have a way of saving a reconstructed model as a scenario.h5 file that artist can read.
Currently when I have reconstructed some heliostats, I save control points and kinematics parameters in seperate files so that I can load them later on, overwrite them in a different scenario and reuse the reconstructed model in other tasks, after the reconstruction run has ended.
**Solution**
A method in the Scenario class to save the current state of the model in artist's HDF5 format. Since the model state exists only in memory during a simulation and is discarded when the run finishes, the method only needs to overwrite the control_points and the kinematics rotation_deviation_parameters in the original HDF5 file, or rather create a new file with the old data, only overwritten in the recoonstructed parts.
Contributor guide
Research direction
Start by locating the Scenario class and the code that reads the original scenario.h5 file. Trace how control_points and kinematics rotation_deviation_parameters are represented, then define the save behavior so existing HDF5 data is preserved while reconstructed values are written to a new or overwritten file. Done means the resulting file can be read by ARTIST with the reconstructed model state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100