-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PETSc stages #8
PETSc stages #8
Conversation
new feature: changing inflow boundary - it can change inflow velocity in a given time. I rewrote reading from dat file - now bvel_velin can be an array and it writes to a different array. In time which is given in a different array(velin_time_delims) it takes corresponding velocity and assigns it as bc.velin. The same function calculates bc.velout as before. It is all similar to function BCGetBGStrainRates. I also added separate folder in tests with example how it can be used. This function doesnt change any workflow in usual models with only one velocity. - To use it specify velin_num_periods (INT) for a numbers of changing periods - velin_time_delims (ARRAY) in Ma for an age when to change for a next period (one less than period number!) - bvel_velin (ARRAY) velocities for specified period With changing face_out parameter to -1, 0 or 1 it is possible to change the behaviour of opposite boundary -"-1" can move the same way (e.g. compress from both sides or pull from both sides), -"0" don 't move opposite direction (as before) -"1" move the same direction (as before) lamem_input file also has been updated
Thanks a lot, this is great! Does the thermal solver also take this little time in the Diffusion solver benchmark? |
No it does not show up there. I put profiler for thermal diffusion in timestep look already. But to measure thermal diffuion in Diffusion solver benchmark I will need to put it in Initial guess part of the code. |
Also note that the adjoint tests fail with this:
this requires fixing. |
ok, now this works and I'm in principle happy to merge it. For consistency it would be good if you can increment the version of LaMEM such that we release a new version (easier when doing benchmarking later). |
Thanks - you also need to change it in the |
Added 4 stages:
I am not sure about Thermal solver since it usually solves very fast.
We should maybe discuss what is the best place to put stages.
Here is a short snippet on run with -log_view now.