#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: minor
Component: SimFactory
Comment (by Steven R. Brandt):
What do you see when you type `free -h`?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: minor
Component: SimFactory
Comment (by Jason Kodish):
I've attached the make.log file here as requested
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: minor
Component: SimFactory
Comment (by Jason Kodish):
<div class="preview-container wiki-content"><!-- loaded via ajax --></div>
<div class="mask"></div>
</div>
</div>
</form>
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: minor
Component: SimFactory
Comment (by Roland Haas):
I just gave the instructions a try on a freshly installed and updated Ubuntu 20.04 VM. I could compile fine followign the instructions from the tutorial, which probably matches \(mostly\) with what Steve’s suggestion would achieve.
So: worksforme.
Since it clearly fails for you, one needs to find out why. Unfortunately the partial error output that was provided is not quite enough to do so. Instead the full build log would be helpful. Namely if you could attach the file `make.log` produced by:
```shell
make sim-realclean
VERBOSE=yes ./simfactory/bin/sim build -j1 sim 2>&1 | tee make.log
```
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: minor
Component: SimFactory
Comment (by Steven R. Brandt):
I didn’t see the original email. He should try running the following:
```
sudo apt-get install -y libjpeg-turbo?-dev gcc git liblapack-dev make subversion g++ libpapi-dev libhwloc-dev hwloc rsync libopenmpi-dev libhdf5-openmpi-dev libssl-dev numactl gfortran libhdf5-dev libfftw3-dev patch libgsl-dev pkg-config
```
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: minor
Component: SimFactory
Changes (by Roland Haas):
priority: minor (was blocker)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: open
Milestone:
Version: ET_2021_05
Type: bug
Priority: blocker
Component: SimFactory
Changes (by Roland Haas):
status: open (was new)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2539: Unable to compile on Ubuntu 20.04 or run executable
Reporter: Jason Kodish
Status: new
Milestone:
Version: ET_2021_05
Type: bug
Priority: blocker
Component: SimFactory
I have attempted to compile the toolkit per [https://github.com/nds-org/jupyter-et/blob/master/CactusTutorial.ipynb](htt…
It goes along until getting to this point and stops:
COMPILING Carpet/CarpetLib/src/prolongate\_4d\_o1\_rf2.cc
make\[2\]: \*\*\* \[/home/cenobyte/Cactus/lib/make/make.thornlib:113: make.checked\] Error 2
make\[1\]: \*\*\* \[/home/cenobyte/Cactus/lib/make/make.configuration:179: /home/cenobyte/Cactus/configs/sim/lib/libthorn\_ML\_CCZ4.a\] Error 2
Creating /home/cenobyte/Cactus/configs/sim/lib/libthorn\_CarpetLib.a
make: \*\*\* \[Makefile:265: sim\] Error 2
Some googling has suggested those errors can be ignored \(Can they be?\), but when I try to run the HelloWorld test example I get this:
./simfactory/bin/sim create-run helloworld --parfile arrangements/CactusExamples/HelloWorld/par/HelloWorld.par
Parameter file: /home/cenobyte/Cactus/arrangements/CactusExamples/HelloWorld/par/HelloWorld.par
Error: Executable /home/cenobyte/Cactus/exe/cactus\_sim for configuration sim does not exist or is not readable
Aborting Simfactory.
Is this because of the failed compile or something else?
Not sure how to fix that.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…
#2538: Inclusion of kuibit
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component:
Changes (by Roland Haas):
kuibit is a Python package for post-processing simulations. The tool comes with several features for analysis and visualization. For some of the most common operations \(e.g., 2D plot of a grid variable, extraction of gravitational waves, ...\), users can directly obtain the result without writing any code. The number of such ready-made scripts grows with every release of kuibit. For everything else, kuibit
has a large number of features \([https://sbozzolo.github.io/kuibit/features.html\)](https://sbozzolo.github.io/kuibit/features.html)\) that can be used in scripts or notebooks.
kuibit is designed to be user-friendly: it has rich documentation \([https://sbozzolo.github.io/kuibit/\),](https://sbozzolo.github.io/kuibit/),\) examples ready to be used, and tutorials. kuibit is also designed to be developer- and maintainer- friendly: it is thoroughly commented, and it implements several continuous integration pipelines to test, document, and publish the package automatically. The high quality of kuibit is also recognized by its publication in the Journal of Open Source Software \([https://joss.theoj.org/papers/10.21105/joss.03099\).](https://joss.theoj.org/papers/10.21105/joss.03099).\)
kuibit is largely inspired by Wolfgang Kastaun's PyCactus. kuibit shares the same overall design with PyCactus, and in some cases, the implementation details too. kuibit would not exist without PyCactus.
As far as I know, 5-10 people are actively using kuibit as their main tool to interface with the output of simulations. The feedback I got is overwhelmingly positive: users that are new to the Einstein Toolkit praise the simplicity of use and the comfort of working in Python; experienced users claim that kuibit allows them to focus on the science instead of the technical details.
kuibit has already been used for publications, see [https://inspirehep.net/literature?sort=mostrecent&size=25&page=1&q=refersto…
kuibit repo: [https://github.com/Sbozzolo/kuibit](https://github.com/Sbozzolo/kuibit)
Comments and feedback are welcomed.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2538/inclusion-of-kuib…