#2059: SimFactory should detect the number of cores automatically
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
SimFactory should detect the number of cores automatically. See pull
request by Mikael Sahrling: https://bitbucket.org/simfactory/simfactory2
/pull-requests/20/simdtpy-detect-number-of-cpus/diff.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2059>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#228: Make it easier for users to create accounts on TRAC
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit trac | Version:
Keywords: |
----------------------------------+-----------------------------------------
Currently, in order to interact fully with TRAC, it is necessary to have a
CCT account. I would prefer that all potential users of the ET/Cactus
TRAC could create accounts. This way, it would be possible for all bug
reporters to be notified of changes to the tickets they create, and makes
it more likely that they will respond to requests for further information
and confirmations of fixes.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/228>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#270: Need web instructions for building on a new machine
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
We should have instructions on the web that explain how to build the
Einstein Toolkit on a new machine, i.e. a machine for which we don't have
a SimFactory entry already. This seems to be a fairly common case for new
users, who rather want to build on their own machine instead of on Queen
Bee.
This should probably concentrate on configuring Cactus first, i.e. on
configuring SimFactory for building a configuration. Job submission etc.
should come later.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/270>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1804: Provide an Einstein Toolkit User Guide
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
We currently have documentation for individual thorns, but there is no
documentation for the toolkit as a whole, describing how best to
accomplish certain tasks. The [http://arxiv.org/abs/1111.3344 Einstein
Toolkit paper] is a good starting point, but it is a static document, and
is not quite at the level of documentation. I propose to take the paper
and convert it into a user guide for the ET. It should not replicate
detailed information already available in thorn documentation (rather it
should link to it), but should provide a high level overview. It should
also contain best practices for working with the ET. This would be the
first point of reference for new users of the toolkit.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1804>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2212: Meudon_Bin_NS parameter eos_table_filepath ignored by LORENE1
---------------------------------+-----------------------------------
Reporter: Roland Haas | Type: defect
Status: new | Priority: major
Milestone: | Component: EinsteinToolkit thorn
Version: development version | Keywords: Meudon_Bin_NS
---------------------------------+-----------------------------------
It seems that only LORENE2 respects the parameter {{{eos_table_filepath}}}
of Meudon_Bin_NS (which is passed on as an env variable
{{{LORENE_TABULATED_EOS_PATH}}} by the Thorn and interpreted by the
modified version of LORENE stored in LORENE2/dist/Lorene.tar).
Either LORENE1 should modified via a patch to support the same
functionality or (less desireable) Meudon_Bin_NS should check the version
of LORENE it is linked against or (even less so) there should be a comment
in param.ccl warning that the parameter is ignored by older versions of
LORENE.
Note that the check needs to be at runtime since we still must be able to
build Meudon_Bin_NS against the old version of LORENE.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2212>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit