#145: EOS_Omni requires HDF5 library. What about if it only uses HDF5 instead?
---------------------------+------------------------------------------------
Reporter: bmundim | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Other | Version:
Keywords: EOS_Omni HDF5 |
---------------------------+------------------------------------------------
At the moment EOS_Omni requires the HDF5 library to read
the nuclear EOS values from a table. Since not all distros have
fortran support for the HDF5 library as a default, I propose
to change this requirement and provide a fall back in case this
support is not present. Perhaps not using the nuclear EOS, or
reading from an ASCII file instead. This could be just a temporary
solution until the HDF5 library build script becomes more robust.
Opinions?
Thanks,
Bruno.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/145>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#136: Don't rebuild external libraries so often
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
One way to keep the external libraries that have been built would be the
following. Create a dummy configuration "ext" where all external libraries
are built. When another configuration is built, it should be easy to
specify to look there for the external libraries, or maybe this should
even be the default.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/136>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#147: Write transition guide for EOS_Omni
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
The Einstein Toolkit pages need a wiki tutorial for switching to EOS_Omni.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/147>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#162: Document CCTK_GFINDEX3D and friends in reference manual
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
I believe the reference manual does not describe any of the CCTK_GFINDEX*
and CCTK_VECTGFINDEX* functions.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/162>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#112: Python version of Simfactory should be made default before next ET release
------------------------+---------------------------------------------------
Reporter: knarf | Owner: mthomas
Type: task | Status: new
Priority: critical | Milestone: ET_2011_06
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/112>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#131: Cactus produces way too much output with SILENT!=no
-------------------------+--------------------------------------------------
Reporter: knarf | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
I frequently find me scrolling through a lot of not necessary output from
Cactus, including a lot of divider lines (___). I propose a mechanism to
disable most of that output. There is currently one parameter which
influences the amount of output from Cactus. If SILENT is set to 'no',
Cactus provides way more output. All other values produce the usual output
(including not setting it). I propose to use this existing variable to
make Cactus less verbose if SILENT ist set to 'yes'. The default is
'undefined', so this would preserve the default Cactus behaviour.
The attached patch attempts to do this: it suppresses divider lines, pre-
and postprocessing infos if SILENT='yes'. I don't like that name though,
as this is still not really silent, as you will still see one line per
compiled file (ala COMPILING /home/frank.loeffler/mcrt/src/main/Banner.c),
but I don't have a better idea right now and could live with it. The other
option would be to introduce another variable (e.g. BRIEF), but then BRIEF
and SILENT could contradict each other.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/131>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#108: LocalInterp and LocalReduce should move to CactusNumerical
-----------------------+----------------------------------------------------
Reporter: anonymous | Type: enhancement
Status: new | Priority: minor
Milestone: | Component: Cactus
Version: | Keywords:
-----------------------+----------------------------------------------------
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/108>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#143: ETK "Chandrasekhar" release: HDF5 "BUILD" option failing on MacOSX +
openmpi.
--------------------------------------+-------------------------------------
Reporter: bernard.j.kelly@… | Type: defect
Status: new | Priority: major
Milestone: ET_2010_11 | Component: Other
Version: ET_2010_11 | Keywords: HDF5 openmpi
--------------------------------------+-------------------------------------
We've recently tried compiling the latest ETK official release
("Chandrasekhar") on our Macbooks. To get a working HDF5 installation
compatible with the build, we've selected "HDF5_DIR=BUILD". This fails,
however. I'm attaching my user-specified Cactus config. options, as well
as the Thornlist used, and the error messages.
My machine is running OSX 10.5.8 (Leopard), and the compiler is openmpi
[i686-apple-darwin9-g++-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5493)],
installed via macports.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/143>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#63: create separate tracs on trac.cactuscode.org and trac.cfdtoolkit.org
--------------------+-------------------------------------------------------
Reporter: knarf | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
--------------------+-------------------------------------------------------
We need separate tracs on trac.cactuscode.org and trac.cfdtoolkit.org,
including ssl certificates and the complete rest of the setup.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/63>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#123: Run a syntax checker in a pre-commit hook
------------------------+---------------------------------------------------
Reporter: eschnett | Owner: mthomas
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
I am getting annoyed by the frequent syntax errors in SimFactory that used
to be caught by Perl and are now not caught by Python. It would be ideal
if syntax checking could be built into SimFactory, so that it executes
automatically during startup if that isn't too slow.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/123>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit