@@ -37,20 +37,6 @@ implementation and exploration of hydrodynamics methods. It is
3737built in a object-oriented fashion, allowing for the reuse of
3838the core components and fast prototyping of new methods.
3939
40- In the time since the first pyro paper [ @pyroI ] , the code has
41- undergone considerable development, gained a large number of solvers,
42- adopted unit testing through pytest and documentation through sphinx,
43- and a number of new contributors. pyro's functionality can now
44- be accessed directly through a ` Pyro() ` class, in addition to the
45- original commandline script interface. This new interface in particular
46- allows for easy use within Jupyter notebooks. We also now use HDF5
47- for output instead of python's ` pickle() ` function. Previously, we used Fortran
48- to speed up some performance-critical portions of the code. These routines
49- could be called by the main python code by first compiling them using ` f2py ` .
50- In the new version, we have replaced these Fortran routines by python functions
51- that are compiled at runtime by ` numba ` . Consequently, pyro is now written
52- entirely in python.
53-
5440The original goal of pyro was to learn hydrodynamics methods through
5541example, and it still serves this goal. At Stony Brook, pyro is used
5642with new undergraduate researchers in our group to introduce them to
@@ -66,6 +52,20 @@ on the Maestro code [@maestro] and the pyro implementation will be
6652used to prototype new low Mach number algorithms before porting them
6753to science codes.
6854
55+ In the time since the first pyro paper [ @pyroI ] , the code has
56+ undergone considerable development, gained a large number of solvers,
57+ adopted unit testing through pytest and documentation through sphinx,
58+ and a number of new contributors. pyro's functionality can now
59+ be accessed directly through a ` Pyro() ` class, in addition to the
60+ original commandline script interface. This new interface in particular
61+ allows for easy use within Jupyter notebooks. We also now use HDF5
62+ for output instead of python's ` pickle() ` function. Previously, we used Fortran
63+ to speed up some performance-critical portions of the code. These routines
64+ could be called by the main python code by first compiling them using ` f2py ` .
65+ In the new version, we have replaced these Fortran routines by python functions
66+ that are compiled at runtime by ` numba ` . Consequently, pyro is now written
67+ entirely in python.
68+
6969The current pyro solvers are:
7070
7171- linear advection (including a second-order unsplit CTU scheme, a
0 commit comments