#235: Improve performance of Fortran index calculations
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
In Fortran, Cactus currently declares grid functions e.g. as (this is the
expansion of DECLARE_CCTK_ARGUMENTS)
REAL*8 gxx (X0metric,X1metric,X2metric)
where X0metric etc. are integers passed into the routine. Each grid
function group has its own, independent size. This has two disadvantages:
1. The compiler does not know that all grid functions have the same size
(namely cctk_lsh), and thus has to perform array index calculations
separately for each group
2. The argument list is longer than neded
The enclosed patch declares grid functions via cctk_lsh. Grid arrays are
still declared independently.
This reduces the code size of e.g. GRHydro/GRHydro_Tmunu.F90 from 6836 to
6241 bytes on my system. I have not attempted to measure a performance
difference.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/235>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#329: SimFactory/ranger-intel11.cfg: Are BLAS and LAPACK compilations on Ranger
optimized?
-------------------------+--------------------------------------------------
Reporter: bmundim | Owner: mthomas
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version:
Keywords: |
-------------------------+--------------------------------------------------
ranger-intel11.cfg now sets BLAS and LAPACK to be built along with the
Cactus and other external libraries. Usually the host system BLAS and
LAPACK are fine tuned to
take advantage of the particular memory hierarchy of the host machine. I
was wondering if this fine tuning is performed when we set BLAS = BUILD or
LAPACK = BUILD, and, in case it is not, if it would be interesting to
define Cactus env variables to set the size of the several cache memories
for example and use it for this necessary fine tuning.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/329>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#271: python simfactory submit creates only the SubmitScript
----------------------------------------------+-----------------------------
Reporter: alexander.beck-ratzka@… | Type: defect
Status: new | Priority: major
Milestone: | Component: Other
Version: | Keywords: simfactory submit
----------------------------------------------+-----------------------------
The python version of simfactory submit creates only the submitScript
called PreparedSubmitScript. The RunScript is created at the moment of the
simfactory run call at the end of the SubmitScript.
So a user has no possibilty to check whether his settings e.g. for mpirun
have been correct or not for all the time where the job is only queued. I
feel this is not a user friendly solution. The RunScript should be created
together with the SubmitScript.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/271>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#326: Update gsl path in Ranger option file to gsl 1.13
---------------------------------------------+------------------------------
Reporter: bmundim | Owner: mthomas
Type: task | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version:
Keywords: Ranger option configuration gsl |
---------------------------------------------+------------------------------
Ranger config file has been updated recently, so I thought to bring to
your attention that gsl library on Ranger now defaults to version 1.13.
Cheers,
Bruno.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/326>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#327: Simfactory: ranger-intel11.run question.
------------------------+---------------------------------------------------
Reporter: bmundim | Owner: mthomas
Type: defect | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
Shouldn't we load intel/11.1 there, since the default on Ranger is
intel/10.1?
Also unless "module load intel/11.1" is in your .login_user, it will fail
to "module load mvapich" since no compiler has been selected.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/327>
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
#367: When a repo URL changes, GetComponents should offer more help
---------------------------+------------------------------------------------
Reporter: eschnett | Owner: eric9
Type: enhancement | Status: new
Priority: major | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
When a repo URL changes, GetComponents currently suggests to check out the
repo from scratch (and presumably delete/ignore the old repo). This is
very inflexible, in particular when the user has changes in the old
repository, which often happens during development.
SVN (and presumably all other VC software) offer commands to update the
URL, so that one can keep the current checkout. Of course, this makes only
sense if this is the same repository that only moved to a new URL, but
this seems to happen often enough.
GetComponents should at least output instructions for updating the URL.
It would be even better if GetComponents detected that new and old repo
are the same, and then update the repo URL by itself.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/367>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#414: --parallel option not documented in GetComponents
---------------------------+------------------------------------------------
Reporter: bmundim | Owner: eric9
Type: defect | Status: new
Priority: minor | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
The --parallel option is not documented in both versions of GetComponents,
the released and development ones.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/414>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#219: ExternalLibraries method should be documented
---------------------------+------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: documentation |
---------------------------+------------------------------------------------
The Cactus documentation
http://einsteintoolkit.org/info/documentation/UsersGuide/UsersGuidech6.html…
(scroll down to Compiling with Extra Packages)
currently tells people to use the "extras" method for enabling access to
external libraries such as HDF5, MPI etc. As I understand it, this method
is deprecated in favour of the ExternalLibraries method, and both should
not be used at the same time for the same library.
The documentation should be updated to describe the ExternalLibraries
method, and the old method description should be moved to an appendix with
a clear warning that this is deprecated.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/219>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit