Comments (12)
When i change the value of maxcellpersurf manually in the grid.cpp file the code runs and restarts fine but when set in the input script it doesn't
from sparta.
I can't seem to reproduce this. Are you sure your global cellmax
command is before the read_restart
command?
from sparta.
in.sphere_start.txt
in.sphere_restart.txt
Here are the two input files I used to test. If I don't set the cellmax then I get this error:
Max cells overlapping any surf = 228
ERROR: Too many cells overlap one surf - set global cellmax (../grid_surf.cpp:284)
So I used global cellmax 300
.
from sparta.
Just to clarify, the global cellmax
command isn't stored by the restart file, so it has to be set again, before the read_restart
command.
from sparta.
@aklothakis I'm going to close this issue since I can't reproduce it, but please let us know if you have more info on this.
from sparta.
Hello there and thank you for your fast response. In the Manual page 321 says that the read_restart command stores global settings. If you check the read_restart.cpp and write_restart.cpp code you can see that indeed the global settings are saved apart from the cellmax setting.
In order to be able to reproduce the issue try restarting the code without the global command (global commands shouldn't be in the restart script because are saved in the restart file) in your restart script. You will see that all the global settings are saved but you will get a message that the cellmax value is not set. But the cellmax value is set in your input script.
This means that the cellmax value is not saved by the write_restart nor read by the read_restart.
from sparta.
OK I see what you are saying now. The surfmax
variable is stored in the restart file but cellmax
is not. There are probably other global commands not included as well, like mem/limit
and particle/reorder
.
from sparta.
Ok i see, never used the mem/limit
or particle/reorder
but i will have a look at them too. In the pool request i have changed the appropriate lines in the code to include the cellmax. Tested it for a several timesteps and it seems to be working. I haven't tested it extensively though.
If you have any specific tests in mind let me know and i will perform them.
Does it sound nice to do a list of which global commands are not included?
I have attached the "modified" restart to reproduce the issue.
Thanks again.
from sparta.
Here are the global commands that are missing from the restart file:
- surfs
- surfgrid
- cellmax
- splitmax
- surftally
- surfpush
- particle/reorder
- mem/limit
from sparta.
Thank you i will have have a look at them and i will submit a pull request when i have something ready.
Meanwhile tested the cellmax for my case for several thousand timesteps now with 200 cores and is still working.....
from sparta.
Thanks for reporting and working on this. I can help out as well if needed.
from sparta.
Here are the global commands that are missing from the restart file:
- surfs
- surfgrid
- cellmax
- splitmax
- surftally
- surfpush
- particle/reorder
- mem/limit
We are planning to fix this in #303.
from sparta.
Related Issues (20)
- Errors when removing surfaces from simulation HOT 4
- Particle count using transparent surface and issue with multiple core processors HOT 3
- tce/qk style HOT 3
- surf_react_adsorb LH1 reaction HOT 2
- Development of improved subsonic boundary condition and mass flow rate boundary condition HOT 9
- Fix emit/surf command fails when using equals-style variable for setting particle number HOT 3
- Configuration to avoid in order to cutcell algorithm to work or bug ?
- move_surf command
- Issue compiling SPARTA on ALCF's Polaris computer with kokkos enabled HOT 5
- Grid cell corner points on boundary marked as unknown HOT 2
- Illegal group command HOT 2
- Outdated documentation pages related to Section 6 of Manual
- Possible typos in adapt_grid manual page HOT 1
- Typo in dump_modify document HOT 1
- Uninitialized variable in stl2surf.py HOT 2
- Questions about using the output of compute isurf/grid etot HOT 3
- write_surf flag + surf2paraview HOT 4
- Temperature calculation error for "vibrate discrete" command HOT 10
- Fokker Plank collision model HOT 1
- Issues with the calculation method for reverse reaction probabilities
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sparta.