Conversation
incorperation of the three photon sequencing algorithims and update of the base class
Test Results 3 files 3 suites 43m 33s ⏱️ Results for commit 5b6e8a8. ♻️ This comment has been updated with latest results. |
|
There seem to be a bunch of unhappy tests in this PR ;-) |
|
Also I am confused about the changed 4D capabilities (that don't seem to have anything to do with sequencing in parts). |
wahln
left a comment
There was a problem hiding this comment.
Did some preliminary rough review.
matRad/matRad_sequencing.m
Outdated
| @@ -1,4 +1,4 @@ | |||
| function resultGUI = matRad_sequencing(resultGUI,stf,dij,pln,visBool) | |||
| function resultGUI = matRad_sequencing(resultGUI,stf,pln,dij,visMode) | |||
There was a problem hiding this comment.
Is there a reason why the dij has become optional? This is a huge change without much benefit it seems.
There was a problem hiding this comment.
it is just because the dij is just used to recalculate the dose based on the new sequenced weight vector, but you could run the sequencing independently
There was a problem hiding this comment.
This could probably still be removed?
matRad/4D/matRad_calc4dDose.m
Outdated
| @@ -1,29 +1,23 @@ | |||
| function [resultGUI, timeSequence] = matRad_calc4dDose(ct, pln, dij, stf, cst, resultGUI, totalPhaseMatrix,accType) | |||
| function resultGUI = matRad_calc4dDose(dij, pln,stf,resultGUI, totalPhaseMatrix) | |||
There was a problem hiding this comment.
why did the argument list chagne so drastically?
There was a problem hiding this comment.
the ct was only used to save the number of ct scenarios and the motion period , this should now be in the pln scenario model and the cst was used for the ax and bx vectors this is taken directly from the dij
There was a problem hiding this comment.
okay let's approach it from the other way: can we avoid the pln struct when using the ct?
I would like to keep pln out of lower-level functions as much as possible, and only pass it to top-level workflow functions (as the pln can, for example, be easily changed in the GUI and lead to inconsistent inputs).
There was a problem hiding this comment.
i think this can be done, but then i need the ct again,
There was a problem hiding this comment.
no acctually i need it to selecect the sequencer and calculate the phaseMatrix if not given, although right now the phaseMatrix is only calculated for ions not photons
There was a problem hiding this comment.
Isn#t this a function that should actually be moved into the IonSequencer?
There was a problem hiding this comment.
it is this was one of the files i deleted, where i just now reverted the delition to make it backwards compatible, i haved pushed the update to this file jet
There was a problem hiding this comment.
Change in the interface destroys downwards compatibility.. Is this necessary?
There was a problem hiding this comment.
i removed it because it was never used in the function
matRad/matRad_sequencingOld.m
Outdated
There was a problem hiding this comment.
Naming the file sequencingOld and the function still sequencing will create problems. I suggest to not change the interface of the sequencing call (with the optional dij at the end) but just keep the old interface (resultGUI,stf,dij,pln,visBool) -> visBool can become visMode, this is still OK just selecting the visMode 1 if it is true.
There was a problem hiding this comment.
similar to above this is an issue of the delition and reverting of the delition that is not completet yet
There was a problem hiding this comment.
What is changed in the submodule? Is this intentional?
Implementation of a class to handle the photon sequencing with the three algorithims siochi, xia, engle as well as an ion sequencer