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

add fvmbook directory with all examples from red book #9

Open
18 of 51 tasks
rjleveque opened this issue Aug 13, 2013 · 2 comments
Open
18 of 51 tasks

add fvmbook directory with all examples from red book #9

rjleveque opened this issue Aug 13, 2013 · 2 comments

Comments

@rjleveque
Copy link
Member

The following can be adapted from the 4.6 versions at http://depts.washington.edu/clawpack/users-4.6/claw/doc/gallery/gallery_book.html

  • chap3/acousimple
  • chap6/compareadv
  • chap6/wavepacket/
  • chap7/acouinflow/ (scott)
  • chap7/advinflow/
  • chap7/standing/
  • chap9/acoustics/interface
  • chap9/acoustics/layered
  • chap10/tvb/ (niket)
  • chap11/burgers/ (jihwan)
  • chap11/greenlight/
  • chap11/redlight/
  • chap12/efix/ (niket)
  • chap12/llf/
  • chap12/nonconservative/
  • chap13/collide/
  • chap16/vctraffic/ (Brisa)
  • chap17/advdiff/
  • chap17/onramp/
  • chap20/burgers/
  • chap20/rotate/
  • chap21/corner/ (brisa)
  • chap21/radialdam/
  • chap22/corner/ (scott)
  • chap22/rp/
  • chap23/acoustics/

The following can be found in the 4.3 book site http://depts.washington.edu/clawpack/clawpack-4.3/book.html

  • chap8/modeqn/
  • chap8/wavepacket/
  • chap9/color/
  • chap9/traffic/
  • chap11/congestion/
  • chap13/dambreak/
  • chap13/slosh/
  • chap13/swhump1/
  • chap13/tworaref/
  • chap13/twoshock/
  • chap15/slowshock/
  • chap15/startup/
  • chap15/wcblast/
  • chap16/bucklev/
  • chap16/fsin/
  • chap17/advreact/
  • chap17/nocommute/
  • chap17/stiffburgers/
  • chap21/acoustics/
  • chap21/radialdamabc/
  • chap22/inclusion/
  • chap22/plate/
  • chap23/advection/
  • chap23/euler/
  • chap23/shallow/
@ketch
Copy link
Member

ketch commented Nov 2, 2014

PyClaw has an fvmbook directory (created long ago) that should be moved over to apps. Where should we put the PyClaw versions? My suggestion would be to put them in the same directory with each Fortran example; in some cases, code can be reused.

Also, I'm thinking of changing the PyClaw versions to self-contained IPython notebooks.

@rjleveque
Copy link
Member Author

+1 to converting to IPython notebooks, and putting them in the same directory as each set of Fortran code sounds sensible to me.

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

No branches or pull requests

2 participants