Trac January 2022

trac@lists.einsteintoolkit.org

2 participants
112 discussions

#2499: New machine thornyflat at WVU
by Maria 20 Jan '22

20 Jan '22

#2499: New machine thornyflat at WVU Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: SimFactory Comment (by Maria): OK. I'll test it out this weekend with the Johnson release and let you know how it goes. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2499/new-machine-thorn…

1 0

#2499: New machine thornyflat at WVU
by Roland Haas 20 Jan '22

20 Jan '22

#2499: New machine thornyflat at WVU Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: SimFactory Comment (by Roland Haas): Unless there are objections I will apply the pull request after 2022-02-03. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2499/new-machine-thorn…

1 0

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server
by Roland Haas 20 Jan '22

20 Jan '22

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit Virtual Machine Comment (by Roland Haas): Long post below, sorry. I understand the difficulty it creates to try and have the same file present instructions for different environments. This, unfortunately, has always been tricky. ON the other hand, maintaining two different versions, is I suspect not going to be doable \(based on what happened in the past\). The issue with maintaining two almost identical sets of instructions is personpower \(e.g., this is why the wiki-based tutorial at [https://docs.einsteintoolkit.org/et-docs/Tutorial\_for\_New\_Users](https:/… is no longer maintained\) needed to keep them in sync. At least with one notebook, there is only one file to keep up to date. Exporting to HTML is not the tricky bit I suspect, to me the trickiest parts were always getting things to work in the notebook and when copying an pasting commands to a terminal window. Having a mechanical \(no human intervention\) way to export a read-only, laptop suitable version from the notebook would be very nice. I just do not see how to easily do it. The “no human intervention” is very important. So far, each time we had a process requiring human action there has always been the need to double check \(so at least review\) results. Case in point tends to be our release announcements. Eg the current one on hyperspace \(this is just the last time I noticed things, not to single out this particular instance, I can also point to instances where the typo etc is mine\) [https://hyperspace.uni-frankfurt.de/2021/12/09/new-einstein-toolkit-release… reads: > The highlights of this release include: > \* The inclusion of a new code in the Toolkit release, Kuibit > \* The inclusion of a new code in the Toolkit release, RePrimAn that is “RePrimAnd” is missing a “d”. This “d” is present in the template source file present at: [https://www.einsteintoolkit.org/about/releases/ET\_2021\_11\_announcement.m… but was removed when editing the file for length to include it in the hyperspace mailing. Ideally all things that are tutorial server specific should be in the cell labelled “Notebook setup” and everything else should be written in such as way as to work on: * the tutorial server * the server used for ET new user tutorials at workshops * in a docker container on people’s laptops * on people’s laptops using jupyter-notebook * as a read-only document from which one can copy and paste commands into a terminal The latter is somewhat important \(for me at least\), since real world use of the ET is not \(yet\) via Jupyter notebooks but via the command line. When we asked how people use the tutorial there were a couple of groups that ask new students to run the tutorial notebook instruction on their laptop / clusters to get started with the ET \(eg this is how we obtained the quick-running TOV parfile\). In that sense our tutorial is more than just a tutorial that lets new users try things out without having to install anything but also a “getting started” document for new ET users in ET using groups. Before deciding on spending time changing the target audience of the notebook it may be good to survey the user community again to see how people use the notebook and if their are any issues with it that prevents them from using it more often. Looking back at the mailing list archive, the last such survey may have been as early as 2015: [http://lists.einsteintoolkit.org/pipermail/users/2015-April/004070.html](ht… so getting an update would be good. ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2577/cactustutorialipy…

1 0

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server
by Gabriele Bozzola 20 Jan '22

20 Jan '22

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit Virtual Machine Comment (by Gabriele Bozzola): Having worked a little bit on it to add kuibit, I think that the tutorial should not try to target both the tutorial server and users' machines. To enable this, the notebook comes with plenty of code that is distracting and make things more complicated that they could be. What we could do is have the ipynb for the tutorial server, and export a variation of it as html for general use, where we clarify that the various paths are example and one can customize them \(like most “traditional” tutorials\). ‌ ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2577/cactustutorialipy…

1 0

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server
by Roland Haas 20 Jan '22

20 Jan '22

1 0

#2549: inlcude FLRWSolver in ET
by Roland Haas 20 Jan '22

20 Jan '22

#2549: inlcude FLRWSolver in ET Reporter: Roland Haas Status: new Milestone: ET_2022_05 Version: development version Type: enhancement Priority: major Component: Changes (by Roland Haas): milestone: ET_2022_05 (was ET_2021_11) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…

1 0

#2549: inlcude FLRWSolver in ET
by Roland Haas 20 Jan '22

20 Jan '22

#2549: inlcude FLRWSolver in ET Reporter: Roland Haas Status: new Milestone: ET_2021_11 Version: development version Type: enhancement Priority: major Component: Comment (by Roland Haas): With the release out in November it is now time again to start looking into this seriously. Hayley do you need any help bringing the code up to readiness? Helvi would you like an additional reviewer to help out with reviewing the code? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…

1 0

#2589: Modernize information about visualization and post-processing
by Roland Haas 19 Jan '22

19 Jan '22

#2589: Modernize information about visualization and post-processing Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: EinsteinToolkit website Comment (by Roland Haas): Applied as git hash [4155961](rhaas80@bitbucket.org/einsteintoolkit/www/commits/4155961147cec9344dde4951029e0122ea53dd60) "index: latest version -> latest release" of [www](rhaas80(a)bitbucket.org/einsteintoolkit/www) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2589/modernize-informa…

1 0

#2589: Modernize information about visualization and post-processing
by Roland Haas 19 Jan '22

19 Jan '22

#2589: Modernize information about visualization and post-processing Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: EinsteinToolkit website Comment (by Roland Haas): Website changes look mostly ok to me \(one request to use “latest release” rather than “latest version” when referring to the ET\). Changes are requested for the notebook pull request. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2589/modernize-informa…

1 0

#2589: Modernize information about visualization and post-processing
by Roland Haas 19 Jan '22

19 Jan '22

#2589: Modernize information about visualization and post-processing Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: EinsteinToolkit website Changes (by Roland Haas): assignee: Roland Haas (was ) responsible: [] (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2589/modernize-informa…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2022