pyclaw
pyclaw copied to clipboard
clawpack
PyClaw is a Python-based interface to the algorithms of Clawpack and SharpClaw. It also contains the PetClaw package, which adds parallelism through PETSc.
This is work in progress, to allow output of only specified components of q. At the moment, it only works for ASCII output. I couldn't find a way to output...
Currently some of the pyclaw/examples/_/_.py scripts are named for the equations they solve, some for the particular problem. We should choose a consistent convention.
The solver kernel language could be automatically determined by inspecting the Riemann solver. Then the user wouldn't need to set it manually.
Some `pyclaw/examples` directories (e.g. `euler/2d`) include multiple examples and so executing ``` cd $CLAW/doc/doc/pyclaw/gallery python make_plots.py ``` executes all of them. The `_plots` directory will end up containing whatever was...
Running the tests and the Rossby_wave.py script produces a `Segmentation fault` using the intel compiler when the setaux routine is called. The segmentation fault occurs immediately when the routine is...
We should call f2py on the fortran files in Classic and eliminate the duplicates in PyClaw.
We should have one place in the docs where we define the APIs for all the main user-provided functions: - before_step - custom BCs - custom aux BCs - others?
Our testing framework currently makes it rather difficult to run a single test directly without nosetests. You have to do something like: ``` tests = test_acoustics_2d_variable_io() test = tests.next() test[0](*test[1:])...
Most settings of the following work in theory but have not been tested: -char_decomp -lim_type