Time stepper schedule - #1748
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
7e3ed02 to
b14f560
Compare
b14f560 to
e787208
Compare
77b3f88 to
02cf984
Compare
4527945 to
774f55c
Compare
8d27c90 to
702149b
Compare
19872dd to
8f05797
Compare
8f05797 to
fd7e51c
Compare
IvarStefansson
left a comment
There was a problem hiding this comment.
Very good. Do we need a tutorial/update of existing? And remember to add to changelog.md. I guess you can resolve most comments fairly easily. Let me know if and when we need to discuss some of them.
b3d6e02 to
2dc2c0c
Compare
ff60756 to
27307eb
Compare
IvarStefansson
left a comment
There was a problem hiding this comment.
Great work on this one, @Yuriyzabegaev! Approving now, feel free to merge if you are confident about resolving comments. Please let me know if you wish to discuss anything.
| raise ValueError("Number of recomputation attempts must be > 0.") | ||
| """ | ||
|
|
||
| self.advanced_schedule: Schedule |
There was a problem hiding this comment.
Why is the attribute called advanced_schedule, not simply schedule?
| Returns: | ||
| Next time step if time < final_time. None, otherwise. | ||
| @property | ||
| def schedule(self) -> np.ndarray: |
There was a problem hiding this comment.
Since this is not a Schedule, I'm wondering if schedule may not be the best name. Is that related to backwards compatibility?
Co-authored-by: Ivar Stefansson <ivar.stefansson@uib.no>
Proposed changes
This PR goes after #1732. The new class
TimeScheduleris introduced to replaceTimeManager.Types of changes
What types of changes does this PR introduce to PorePy?
Put an
xin the boxes that apply.Checklist
Put an
xin the boxes that apply or explain briefly why the box is not relevant.pytestwas run with the--run-skippedflag.