Initial temperature ascii data model

Hi,
I am running 2D spherical shell models and I’m trying to figure out the best way to output data (specifically the temperature field) of an already completed model to then use as input for the initial temperature field of a new 2D spherical shell model. I’ve done this before in a box model by saving the data from Paraview and organizing it into a .txt file with just the points and temperature columns which I then use as input.
The issue with the 2D spherical seems to be that the data is outputted in Cartesian x,y,z format but wants to read in spherical coordinates. I’m also having a hard time figuring out the necessary number of points for the header of the input file in a 2D shell. Is there a simpler way to do this?
Thanks,
Erin

Hi Erin,

Thanks for posting to the forum!

First, a question - is there a reason why using the checkpointing files as an initial condition simulation would not work? You can always make a new folder with the correct sub-directory structure (output, output/solution, etc, etc) and put the checkpointing files in the correct place within the new folder.

I do this frequently for models where the initial phase of deformation is used as the starting condition for a new series of models with different boundary conditions.

If for some reason the checkpointing files won’t work, my advice would be to use the same method ASPECT uses for converting cartesian to spherical coordinates:

As to what is going wrong with format of the .txt file, can you provide an error message?

I imagine you have seen the various examples:

Cheers,
John

Ah I didn’t realize just putting the checkpoint/restart files in a new directory would still work. That’s way simpler than what I was trying to do. Thanks John!

Sure thing, let us know if you run into any trouble getting this to work!

  • John

Hi John,

I’m trying to restart a model with different conditions from the initial phase as you mention here and I had some questions on executing it since it’s the first time.

Are the files with “restart.*” the only ones needed in the new folder? Also, what are the files with the .old extension and are they needed as well?

Thanks!
Stephanie

Also, can you restart in debug mode from a model that ran in optimized mode?

I was able to successfully restart from a previous run by making a directory and copying the restart files (excluding .old) as well as the solution/ directory. I also changed the start time of the subsequent run to the end time of the first run.

Hi Stephanie,

Great that you were able to get the restart working! You actually do not need to change the start time of the restarted model, but I don’t think it would produce any issues by doing so. However, maybe worth checking to make the output times in the log and solution files are correct.

Regarding switching between debug/release during a restart - I’m not sure if this works and I don’t recall someone testing this previously. There may be some minor differences between debug/release that produce a change in the solution (ex: catching FPEs), but the restart may still work. You definitely would want to make sure the debug/release versions are built from the same branch/commit.

If you have time, it would be great if you try restarting in debug mode after an initial run in release mode. If this works it would be a useful debugging tool for large simulations.

Others may weigh on this point as well.

Cheers,
John

OK, I’ll give it a try and let you know how it goes.

Thanks!
Stephanie

All:
we intended for debug and release builds to be binary compatible, and as a consequence restarts from one to the other should work. If they don’t, that’s a bug.
Best
W.

It’s working fine for me!