#631: Documentation fails to build
---------------------+------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Cactus | Version:
Keywords: |
---------------------+------------------------------------------------------
With the current ET, I cannot build the documentation:
[ianhin@login-damiana EinsteinToolkit]$ make AllDoc
Creating user documentation UsersGuide.pdf
Running pdflatex....
! Argument of \CA@getsvndate has an extra }.
! Paragraph ended before \CA@getsvndate was complete.
! Argument of \CA@getsvndate has an extra }.
! Paragraph ended before \CA@getsvndate was complete.
! Paragraph ended before \@parse@version was complete.
! Missing number, treated as zero.
! Missing = inserted for \ifnum.
! Missing number, treated as zero.
! LaTeX Error: Missing \begin{document}.
! Undefined control sequence.
Problem in . See doc/UsersGuide/LATEX_MESSAGES.
make: *** [UsersGuide] Error 1
I am attaching LATEX_MESSAGES. I have tried this both on damiana and on
my laptop. I consider this a blocker issue which could delay the release.
We must have working documentation.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/631>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#517: archive CactusExternal
-------------------------+--------------------------------------------------
Reporter: knarf | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
We should move the CactusExternal thorns to archive. They cause trouble
and confusion where they are right now. This should happen for the next
Cactus release.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/517>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#176: Test parameter files without running them
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
It would be useful to be able to check that the parameters of a run are OK
before running it. Since there can be long queue times on supercomputers,
it would be good to do this on a local machine which might not have as
much memory as is required for the full run. Currently, running the job
would cause memory exhaustion on the smaller machine.
One solution would be an additional command-line argument to Cactus
--exit-after-paramcheck which stops the run cleanly after the PARAMCHECK
Cactus bin. This is preferable to a new Cactus parameter, as it would not
require the parameter file to be modified. One could imagine this also
being potentially used by simfactory automatically when submitting a job
(though this would only work if you could run MPI executables on the head
node).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/176>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#773: McLachlan dissipation should be disabled by default
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
In the current version of McLachlan, the parameter apply_dissipation is
set to "always" by default. The corresponding "epsdiss" is set to 0 by
default. The dissipation calculation in McLachlan is expensive due to the
way that it iterates over variables. Use of the Dissipation thorn or
similar is usually much faster. I had not realised that apply_dissipation
was "always" by default. I think it should be "never".
OK to change? (with announcement to the mailing list)
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/773>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#535: Add autoconf macro to test C99 style variable declarations
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
Many compilers don't support C99 style variable declarations in their
default settings. We should test this, add certain flags automatically if
we can, or abort with a clear error message otherwise.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/535>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#632: Changegroup hook failed when pushing to Carpet repository
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
When I push to the Carpet repository, I get the following message:
{{{
remote: error: changegroup.cia hook failed: http://cia.vc returned an
error: queued.
}}}
The push succeeds. What is the cause of this error?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/632>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#412: Split Appendices
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
Currently, the appendices of the users' guide are repeated into the
reference manual. This is somewhat confusing, and causes problems because
the appendices cannot easily reference other sections (e.g. "see page 15"
doesn't make sense since one doesn't know in which document this will be
read). I suggest to split the appendices and have some of them in the
users' guide while moving others into the reference manual, so that each
appendix is included in only one document
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/412>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#704: Carpet complains about lack of mpi after ExternalLibraries/OpenMPI is built
---------------------+------------------------------------------------------
Reporter: bmundim | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
---------------------+------------------------------------------------------
I was able to compile ExternalLibraries/OpenMPI successfully, but the
Cactus
compilation stops afterwards with the message:
/home/bruno/tmp/einstein_dev_maxwell/Cactus/arrangements/Carpet/CarpetLib/src/make.configuration.defn:5:
*** Configuration error: The Carpet thorns require MPI. Please configure
with MPI, or remove the Carpet thorns from the ThornList.. Stop.
make: *** [einstein] Error 2
I indicated in my configuration file the following options:
OPENMPI_DIR = BUILD
OPENMPI_INSTALL_DIR = /home/bruno/local/gcc4.6.1/openmpi-1.5.4
I have then tried to indicate in my config file these extra options
after the library was built (and the rest of Cactus compilation stopped):
OPENMPI_DIR = /home/bruno/local/gcc4.6.1/openmpi-1.5.4
OPENMPI_INC_DIRS = /home/bruno/local/gcc4.6.1/openmpi-1.5.4/include
OPENMPI_LIB_DIRS = /home/bruno/local/gcc4.6.1/openmpi-1.5.4/lib
The config-info file does reflect these choices afterwards, and apparently
the flag indicating the presence of mpi library, HAVE_MPI, was set
correctly
at ~/Cactus/configs/einstein/bindings/Configuration/Capabilities:
grep -i have_mpi *
cctki_MPI.h:#define HAVE_MPI 1
make.MPI.defn:HAVE_MPI = 1
however since I didn't use the old mechanism to tell Cactus about MPI, the
~/Cactus/configs/einstein/config-data/make.extra.defn doesn't have
anything
indicating the presence of mpi library there.
It seems to me a compilation order issue. Somehow HAVE_MPI definition is
coming
after Carpet compilation, triggering this error then.
Does anyone have any idea where I should look at in order to fix this
problem?
Thanks,
Bruno.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/704>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#720: check at runtime that all REQUIREd and OPTIONAL thorns and capabilities are
active
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
This is an offshot of a discussion on the Cactus developers mailing list:
http://cactuscode.org/pipermail/developers/2011-November/006258.html
On 6 Jan 2012 12:54:13 -0500 eschnett said:
> What is currently missing is the mechanism that checks that all thorns
> providing required capabilities are activated. If they are not, code
> in inactive thorns is called -- this is fine as long as no Cactus
> infrastructure is used (parameters, scheduled routines, grid
> functions, etc.).
>
> Yes, we should implement the respective checks; yes, we should
> automatically activate thorns required for capabilities (and maybe
> some others as well?); yes, we should then output this thorn list to
> the screen (done anyway) and into a file.
>
> By the way, Cactus already determines which thorns need to be
> activated automatically as a service to the user in the error message
> that complains about missing thorns.
The idea seems to be to document all thorns whose code is executed in the
parameter file.
Ian's original need might be served by an "OPTIONAL" statement in
configuration.ccl
(http://einsteintoolkit.org/documentation/UsersGuide/UsersGuidech12.html#x17…)
and some #ifdefs, maybe.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/720>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit