Add svZeroDCalibrator input file generation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- tooling
Research direction
This is an open design discussion, not a scoped task: the author asks how to reconcile svZeroDCalibrator input-file generation with svSlicer and svSuperEstimator into one 3D-to-calibrated-0D pipeline, without committing to an approach. Start by reading the linked svZeroDSolver documentation section on the 0D solver calibrator and the two external repositories (svSlicer, svSuperEstimator) to see the existing formats, then summarise options in the thread. There is no defined deliverable yet, so 'done' means the maintainers agree on a workflow before any code is written.
Written by the indexing model from the issue text.
Description
Problem
Currently the user must generate the svZeroDCalibrator input file (described here in the documentation). This requires the user to manually add the calibration target time series and it's temporal derivative to the 0d json file. Although the advent of robust AI tools had made this easier, it is still unintuitive and limits the usefulness of the 0D calibrator.
Solution
As far as I am aware the main use case of the calibrator is to calibrate a 0d model against a 3D result, in which case the user should only need to provide a 3D result and the matching centerlines. Then we could call svSlicerto generate the projected centerline result and then a script to convert it into the calibrator input file.
however this becomes more of a "pipeline" than an application once we start calling svSlicer. additionally this overlaps a workflow already provided by svSuperEstimator
I think it is time to reconcile these different tools together and figure out the most efficient way to provide an intuitive and efficient workflow from 3D simulation -> calibrated 0d model.
I am open to any and all suggestions on how to structure this workflow and where to access it.
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct and Contributing Guidelines
- Dominant language
- C++
- Stars
- 22
- Forks
- 45
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SimVascular/svZeroDSolver
-
Incomplete Implementation for Windows OS in svzerodsolver.cpp: Reads input files but does not save path for output.csvPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SimVascular/svZeroDSolver#238 · 6 comments ·
-
Add AGENTS.mdOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SimVascular/svZeroDSolver#232 · 1 comment ·
-
CI fails fetching Eigen from GitLab under loadPossibly taken @zasexton claimed this 1 day ago. Openbug
Difficulty 3/5 Half a day Newbie friendliness 30/100
SimVascular/svZeroDSolver#255 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
SimVascular/svZeroDSolver#246 ·
-
Strain-dependent active stress modelPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 48/100
SimVascular/svZeroDSolver#244 ·
All issues in SimVascular/svZeroDSolver
Similar issues
-
v9.6.0: CMake incorrectly enforces presence of libevdevPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Rowan (2017) electron heating gives NaN for beta > beta_max; clip() then sets electrons to kel_minOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
parthenon-hpc-lab/kharma#213 · 1 comment ·
Maintainers usually reply within 3 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metasequoiaime/msime#9113 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tone-3000/tone3000-plugin#257 · 1 comment ·
Maintainers usually reply within 1 day
-
Locked plugin flip-flops position on every refresh after being disabledPossibly taken @Illustar0 claimed this today. Openissue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ModOrganizer2/modorganizer#2449 ·