Skip to content
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

Refactor valout routine #202

Merged
merged 19 commits into from
Jun 15, 2018
Merged

Refactor valout routine #202

merged 19 commits into from
Jun 15, 2018

Conversation

mandli
Copy link
Member

@mandli mandli commented Jul 31, 2017

This refactor is the basis of an effort to add other output formats, in particular either HDF5, SILO, and/or NetCDF.

@mandli
Copy link
Member Author

mandli commented May 29, 2018

This PR now incorporates the recording of timing as outlined in clawpack/geoclaw#280. A couple of things:

  • Does the output look ok?
  • It was mentioned that we may want to also move the timing from fort.amr to it's own file as well.

Once this is figured out we can also add this to GeoClaw.

@rjleveque
Copy link
Member

rjleveque commented Jun 4, 2018

Yes, I think what now appears at the end of fort.amr with overall timing info could go to a new file timing.txt.

I like the timing.csv format, but it seems like a column is missing for total wall time?

I will update my plot_timing_stats.py from clawpack/geoclaw#280 to read in this file.

The original point of this PR was to support HDF5, is this part fully working?

@mandli
Copy link
Member Author

mandli commented Jun 4, 2018

  • I will modify this PR to pipe the output into a file called timing.txt.
  • I thought total wall time was being recorded, will look.
  • It was but I think all of this works independently of that right now and I think it’s better merge than to wait for that to happen.

@rjleveque
Copy link
Member

We also need a column in timings.csv for the simulation time (the value printed to fort.t*) at each output time, since the plots show e.g. CPU time vs. simulation time.

@mandli
Copy link
Member Author

mandli commented Jun 5, 2018

Does the line call cpu_time(t_CPU_overall) not get the simulation time?

@mandli
Copy link
Member Author

mandli commented Jun 5, 2018

I modified the end of amr*.f90 to output to a separate file.

rjleveque added a commit to rjleveque/visclaw that referenced this pull request Jun 9, 2018
rjleveque added 4 commits June 8, 2018 21:17
required adding new module variable to amr_module.f90
Note that timing is done differently in 1d than 2d, does not yet support restart
As in 1d, this needs further work to allow restart
@rjleveque
Copy link
Member

Don't merge until mandli#2 is merged in to this.

@rjleveque
Copy link
Member

rjleveque commented Jun 15, 2018

I am going to merge this, but at some point more work is needed to make restarting timers work in 1d and 3d, see #219.

See also the discussion in mandli#2

@rjleveque rjleveque merged commit 7191037 into clawpack:master Jun 15, 2018
mandli pushed a commit to clawpack/visclaw that referenced this pull request Aug 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants