#880: Improve McLachlan documentation
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
There should be documentation for the McLachlan arrangement. There is
currently documentation at
http://www.carpetcode.org/gitweb/?p=McLachlan.git;a=blob;f=doc/mclachlan.te…)
but this is mostly installation instructions, which is not relevant for
most users of the ET. This documentation is not built as part of the
normal documentation build process.
1. Add standard Cactus arrangement documentation;
2. Transfer relevant information from mclachlan.tex;
3. We should probably follow the usual thorn documentation template for
this arrangement documentation, simultaneously describing all the thorns.
We should explain precisely what formulation is evolved (possibly by
reference to the .m file, but it would be nice for users not to have to
browse through source code).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/880>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#841: MoL flag for last MoL_PostStep
----------------------------------------+-----------------------------------
Reporter: reisswig@… | Type: enhancement
Status: new | Priority: optional
Milestone: | Component: Cactus
Version: | Keywords: MoL last PostStep flag
----------------------------------------+-----------------------------------
This patch adds a flag MoL_LastPostStep which indicates whether we are in
the last MoL_PostStep.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/841>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#845: no more links to mailing lists on website
-------------------------------------+--------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
It seems as if in the restructuring of the website we lost the page
listing all the mailing lists available:
http://einsteintoolkit.org/about/community/
Two of the four lists appear in
http://einsteintoolkit.org/community/support/ now, but the trac list and
announce list are not visible anymore.
They should be added to the support page.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/845>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#876: Allow optional thorns in the thorn list
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
Some thorns are not available everywhere, yet we want to provide a single
thorn list for all systems. We discussed the following mechanism:
- There is a way to indicate optional thorns in the thorn list, e.g. via a
prefix "!OPTIONAL". These thorns are disabled by default.
- There is a way to enable these thorns in the option list. The option
list is a good place for this since it is already machine specific. This
mechanism should mesh nicely with how options for that thorn are
specified.
- These specifications in the option list are interpreted by Cactus (not
Simfactory), and modify the thorn list before it is interpreted (by
Cactus).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/876>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#588: simfactory tries to create the scratch directory when submitting the job
------------------------+---------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
on some machines the desired scratch directory is not visible from the
head node but is compute node local (eg. kraken I think or zwicky for
sure).
Simfactory should not try to create the scratch directory on the node that
runs qsub but rather inside of the runscript or submitscript.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/588>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#860: Don't rmtree(scratchdir)
---------------------------+------------------------------------------------
Reporter: barry.wardell | Owner: eschnett
Type: defect | Status: new
Priority: blocker | Milestone:
Component: SimFactory | Version:
Keywords: |
---------------------------+------------------------------------------------
The mdb in SimFactory has an entry for scratchdir. If scratchdir is a
relative path, it is assumed to be relative to the restart output
directory. It's not clear exactly what the purpose of this is, but
SimFactory does the following things with it:
1. Create the directory at the start of a simulation if it doesn't exist.
2. Delete the entire directory using rmtree(scratchdir) during "cleanup".
This happens, for example, when an existing simulation is restarted.
The second of these seems very dangerous to me and I think it should be
removed. In particular, if you happen to have scratchdir set to be the
same for more than one simulation (by setting it to, e.g., /scratch), this
scrachdir for all simulations will be erased as soon as one simulation
does a cleanup.
I recently had an even worse experience where I was using /scratch as my
basedir and /scratch also happened to be set as the scratchdir in the mdb
for that machine. All of my simulations on that machine had only a single
restart, so all was well until I tried to restart one simulation and
instead of doing so SimFactory erased all of my simulations on the
machine.
While I can admit to user error in this case (I also wrote the machine
entry), I think the goal of SimFactory should be to err on the side of
caution and shouldn't do this blind rmtree of whatever scratchdir is set
to.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/860>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#733: Provide complete EVO meeting description on web pages
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: blocker | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
The full EVO meeting descriptions should be on the ET web and wiki pages
and in emails. If e.g. the meeting name is missing, one has to stop evo,
follow the link which restarts evo, etc. If the phone number is missing,
then it is very difficult to call in without using starting EVO.
In particular, the page <http://einsteintoolkit.org/seminars/2012_01_16/>
has only a cryptic url and no other information. The announcing email only
pointed to this page.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/733>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#703: Failure to build h5check on datura
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
--------------------+-------------------------------------------------------
When building the Einstein Toolkit thornlist on Datura, the utilities fail
to build with the error:
make[1]: No rule to make target
`/Users/barry/Research/Cactus/AEI/exe/sim/h5check', needed by `utils'.
Stop.
make[1]: Waiting for unfinished jobs....
cc1plus: warning: command line option '-std=c99' is valid for C/ObjC but
not for C++ [enabled by default]
make: *** [sim-utils] Error 2
datura.cfg has
HDF5_DIR = /cluster/hdf5/SL6/1.8.7-intel11.1.072all
Any ideas what might cause this problem?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/703>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#823: Create changelog for upcoming ET release
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: hinder
Type: task | Status: new
Priority: major | Milestone: ET_2012_05
Component: Other | Version:
Keywords: |
--------------------+-------------------------------------------------------
We need a changelog for the upcoming ET release. I have a script to
generate this. I will run it.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/823>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#819: an external library to support sqlite
-------------------------+--------------------------------------------------
Reporter: jtao | Owner:
Type: enhancement | Status: new
Priority: optional | Milestone: Cactus_4.1.0
Component: Cactus | Version: Cactus_4.0.0
Keywords: |
-------------------------+--------------------------------------------------
as the title
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/819>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit