Trac May 2018

trac@lists.einsteintoolkit.org

1 participants
62 discussions

[Einstein Toolkit] #2139: The initial data used in arXiv: 1304.5544 are not downloadable now.
by Einstein Toolkit 24 May '18

24 May '18

#2139: The initial data used in arXiv: 1304.5544 are not downloadable now. ---------------------------------+------------------------------------- Reporter: kidcheong@… | Type: defect Status: new | Priority: unset Milestone: ET_2018_02 | Component: EinsteinToolkit website Version: development version | Keywords: ---------------------------------+------------------------------------- I tried to run the code and reproduce the examples in arXiv: 1304.5544 [gr-qc]. In the rotating core-collapse part, I found that once I tried to download the file "ID_A3_oct.h5.xz (221Mb)", "ID_A3_oct_64.h5.xz (388Mb)" and "ID_A3_oct_80.h5.xz (747Mb)" in http://einsteintoolkit.org/mp.html, the website shows the following: ---- 404 Not Found Not Found The requested URL /~rhaas/ET/2013_MHD/collapse/ID_A3_oct.h5.xz was not found on this server. Apache/2.2.15 (Red Hat) Server at www.tapir.caltech.edu Port 80 ---- Where can I download them? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2139> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #2148: captcha on trac.einsteintoolkit.org broken
by Einstein Toolkit 23 May '18

23 May '18

#2148: captcha on trac.einsteintoolkit.org broken ---------------------------------+------------------------------------- Reporter: Roland Haas | Type: defect Status: new | Priority: blocker Milestone: | Component: EinsteinToolkit website Version: development version | Keywords: trac catcha ---------------------------------+------------------------------------- The CAPTCHAs on trac.einsteintoolkit.org seem completely broken. If I try to create a new ticket and am not logged in I am first presented by a screen with a red box and a google "I am human" clickbox, yet clicking on the box does give another page with only the red box and nothing else. Note that this happens *after* I have gone through all the work of entering text for my ticket etc and that text may be lost (depends on the browser I guess). So this should be fixed a soon as ever possible, at least if this is not just something that affects only my browser. First page shown: [[Image(2018-05-10T113644.png)]] Second page shown: [[Image(2018-05-10T113655.png)]] -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2148> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #502: SimFactory user-guide should be available and updated automatically
by Einstein Toolkit 22 May '18

22 May '18

#502: SimFactory user-guide should be available and updated automatically -------------------------+-------------------------------------------------- Reporter: hinder | Owner: knarf Type: enhancement | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- SimFactory has an incomplete user guide in the doc/userguide directory. This is developed using Sphinx, which is a Python framework for writing documentation. You need to install sphinx to generate this documentation. This can be done using something similar to the following: export PYTHONPATH=/home/ianhin/software/python export PATH=/home/ianhin/software/python/:$PATH hash -r easy_install --install-dir ~/software/python sphinx Then go into the simfactory/doc/userguide directory and type: ./autogen make html to generate HTML documentation (type just "make" to see the other possible targets like PDF etc). This should be regenerated on any commit to the SimFactory/doc/userguide directory and copied to a web-accessible location for inclusion on simfactory.org. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/502> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #1698: The ET tickets should be tidied up
by Einstein Toolkit 22 May '18

22 May '18

#1698: The ET tickets should be tidied up ----------------------------------+----------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit trac | Version: development version Keywords: | ----------------------------------+----------------------------------------- Many of the ET tickets have not seen much attention recently or at all. We should have a session where we run though all the tickets and make sure that their priorities/state etc are correct. Once we have done this, we should come up with a strategy for keeping the tickets under control. In the process, we should decide what is meant by the different ticket priorities, and whether we need to add additional priorities or states to allow us to more effectively manage the tickets. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1698> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #719: Mailing lists could have a link to the archived version of the message
by Einstein Toolkit 21 May '18

21 May '18

#719: Mailing lists could have a link to the archived version of the message -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | -------------------------+-------------------------------------------------- It would be useful for the footer of a mailing list posting to contain a URL to the archived version of the message so that it is easy to point people to the message in an email. This would apply to both the Cactus and the ET lists. It appears that this is not straightforward in MailMan 2, but is expected in version 3: http://mail.python.org/pipermail/mailman- users/2011-October/072378.html. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/719> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 18

[Einstein Toolkit] #2152: simfactory's core detection code fails catastrophically for LANG=zh_CN.utf8
by Einstein Toolkit 14 May '18

14 May '18

#2152: simfactory's core detection code fails catastrophically for LANG=zh_CN.utf8 ---------------------------------+--------------------------- Reporter: Roland Haas | Type: defect Status: new | Priority: major Milestone: | Component: Other Version: development version | Keywords: GetComponents ---------------------------------+--------------------------- There is a report on the ET mailing list (http://lists.einsteintoolkit.org/pipermail/users/2018-May/006250.html) about simfactory failing. This can be worked around by setting LANG=C LC_ALL=C (or an English locale for that matter). Naturally the code in simfactory only works for English locales since it parses the field names and looks for only English names of the field so eg: {{{ $ LANG=de_DE.utf8 simfactory/bin/sim setup-silent Unknown machine name ekohaes8.ncsa.illinois.edu Warning: Cannot find Number of Cores per CPU, using default 1 }}} which is expected. However setting LANG to a Chinese locale gives an error that aborts the code: {{{ LANG=zh_CN.utf8 simfactory/bin/sim setup-silent Unknown machine name ekohaes8.ncsa.illinois.edu Here we will define some necessary Simulation Factory defaults. Determining local machine name: ekohaes8.ncsa.illinois.edu Traceback (most recent call last): File "simfactory/bin/../lib/sim.py", line 148, in <module> main() File "simfactory/bin/../lib/sim.py", line 144, in main CommandDispatch() File "simfactory/bin/../lib/sim.py", line 106, in CommandDispatch module.main() File "/data/rhaas/postdoc/gr/cactus/ET_trunk/repos/simfactory2/lib/sim- util.py", line 266, in main CommandDispatch() File "/data/rhaas/postdoc/gr/cactus/ET_trunk/repos/simfactory2/lib/sim- util.py", line 51, in CommandDispatch exec("command_%s()" % command) File "<string>", line 1, in <module> File "/data/rhaas/postdoc/gr/cactus/ET_trunk/repos/simfactory2/lib/sim- util.py", line 100, in command_setup_silent dt.begin() File "/data/rhaas/postdoc/gr/cactus/ET_trunk/repos/simfactory2/lib/simdt.py", line 135, in begin self.action(dd) File "/data/rhaas/postdoc/gr/cactus/ET_trunk/repos/simfactory2/lib/simdt.py", line 186, in action results = eval("self.macro_%s" % action) File "<string>", line 1, in <module> File "/data/rhaas/postdoc/gr/cactus/ET_trunk/repos/simfactory2/lib/simdt.py", line 471, in macro_CREATE_MACHINE cpu_info[l[0]] = l[1].strip('.\n ').strip('kB') IndexError: list index out of range }}} which should not happen. No matter the error, simfactory must at worst revert to "1 core per cpu" settings since it is the very first thing that people execute when using the ET. The issue ends up being that the Chinese locale uses a different ":" symbol that looks visually similar but (seems to) has the same width as a Chinese character and not that of a Latin one: {{{ 架构： x86_64 }}} where the difference is between "：" and ":". A simple fix may be to try and call lscpu with the "C" locale which must always exist (see https://www.gnu.org/software/libc/manual/html_node /Choosing-Locale.html). A similar issue may exist in other places where we parse command output. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2152> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #2153: Test ticket
by Einstein Toolkit 14 May '18

14 May '18

#2153: Test ticket ---------------------------------+-------------------- Reporter: anonymous | Type: defect Status: new | Priority: unset Milestone: | Component: Other Version: development version | Keywords: ---------------------------------+-------------------- Test -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2153> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2150: jupyter tutorial uses create-run to run TOV simulation in foreground
by Einstein Toolkit 11 May '18

11 May '18

#2150: jupyter tutorial uses create-run to run TOV simulation in foreground -------------------------------------+--------------------------------- Reporter: Roland Haas | Owner: Roland Haas Type: defect | Status: assigned Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: new-user-tutorial | -------------------------------------+--------------------------------- create-run is not something that is typically used on clusters and also is not what is used for the "Hello, World!" example before. For the sake of keeping the information presented to new users minimum, we should not use it. Keeping the run in the background also means that we can increase runtime and still do plots every once in a while to show the oscillations. One cal also use "show-oputput --follow" to show the progress of the simulation I think. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2150> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #2149: jupyter tutorial only evolves TOV star for very short time
by Einstein Toolkit 11 May '18

11 May '18

#2149: jupyter tutorial only evolves TOV star for very short time -------------------------------------+--------------------------------- Reporter: Roland Haas | Owner: Roland Haas Type: defect | Status: assigned Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: new-user-tutorial | -------------------------------------+--------------------------------- It sets the evolution end time to 250Msun which is barely enough to see one oscillation. Setting it to something so short makes no sense. Once can always abort if one wants to stop it. We should restore the original final time. This is the graph produced: [[Image(index.png)]] -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2149> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2147: new user tutorial does not show expected plot
by Einstein Toolkit 10 May '18

10 May '18

#2147: new user tutorial does not show expected plot -------------------------------------+--------------------------------- Reporter: Roland Haas | Owner: Roland Haas Type: enhancement | Status: assigned Priority: minor | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: new-user-tutorial | -------------------------------------+--------------------------------- The new users' tutorial (see eg https://nbviewer.jupyter.org/github/nds- org/jupyter-et/blob/master/CactusTutorial.ipynb) does not contain any image of the "expected" output anymore, the way the old tutorial did (see eg https://docs.einsteintoolkit.org/et- docs/Simplified_Tutorial_for_New_Users#Look_at_Results). This is bad because it does not give any indication as to whether the obtained results is even reasonable. The notebook should contain either the output for the image (and only that output) or some embedded data that is plotted to show the expected plot (which I would prefer but do not know how feasible this is). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2147> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac May 2018