#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: open
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
Sure. Note that the `numpy` ↔︎ Python compatibility issue does not directly arise with those clusters I would claim. The old clusters only providing old Python will provide an equally old \(and compatible to Python\) `numpy`. So the issue would be more whether `kuibit` can support both old and new `numpy` versions. From previous discussion about this my understanding is that supporting both numpy versions is \(basically\) impossible in kuibit. So faced with the choice of having to drop support for some version of `numpy` dropping support for the older one rather than dropping support for all newer versions makes sense.
This has been an issue with old HPC clusters all the time, they just offer quite old software stacks.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: open
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Gabriele Bozzola):
kuibit’s discovery mechanisms can be slow on distributed filesystems when there are lots of small files \(for ASCII files, kuibit opens every file and does regular expression matching to find what’s inside\). I wrote some recommendations here
[https://sbozzolo.github.io/kuibit/faq.html#some-of-the-attributes-in-simdir…
It is also a good idea to use HDF5 whenever possible \(eg for waveform and horizon data too\)
‌
Note also that Python 3.6 end of life was 2021. Numpy dropped support from Python 3.6 in 2020 \(version 1.20\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2805: README file rebuild instructions missing package
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: trivial
Component: EinsteinToolkit thorn
Changes (by Roland Haas):
The current instructions in Baikal to regenerate code say
```shell
pip install sympy==1.11
git clone https://github.com/zachetienne/nrpytutorial.git
cd nrpytutorial
git checkout b60bba29582ae563aaae5340638674ce8ddc2c79
cd BaikalETK
make
```
which, when done in a virtualenv \(to actually control sympy version\) fails due to missing `ipython`. One should should thus install both sympy and ipython
```shell
python3 -m venv $PWD
source bin/activate
pip install sympy==1.11 ipython
git clone https://github.com/zachetienne/nrpytutorial.git
cd nrpytutorial
git checkout b60bba29582ae563aaae5340638674ce8ddc2c79
cd BaikalETK
make
```
‌
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2805/readme-file-rebui…
#2805: README file rebuild instructions missing package
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: trivial
Component: EinsteinToolkit thorn
The current instructions in Baikal to regenerate code say
```shell
pip install sympy==1.11
git clone https://github.com/zachetienne/nrpytutorial.git
cd nrpytutorial
git checkout b60bba29582ae563aaae5340638674ce8ddc2c79
cd BaikalETK make
```
which, when done in a virtualenv \(to actually control sympy version\) fails due to missing `ipython`. One should should thus install both sympy and ipython
```shell
python3 -m venv $PWD
source bin/activate
pip install sympy==1.11 ipython
git clone https://github.com/zachetienne/nrpytutorial.git
cd nrpytutorial
git checkout b60bba29582ae563aaae5340638674ce8ddc2c79
cd BaikalETK make
```
‌
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2805/readme-file-rebui…
#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: open
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
though, simple test to use that module so far is failing. With an illegal instruction error not less. Very odd.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: open
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
Ok, so that bumps the minimum version from 3.6 to 3.7. Just taking a look at what I think may be the oldest cluster in ACCESS-CI \(SDSC’s expanse\), it has a module for python 3.8 and runs python3.6 as a system package. So should \(TM\) be fine, though one assumes one will need to install `kuibit` in a `virtualenv` and have `pip` install all dependencies while providing a correct say `libhdf5` module.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: open
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Gabriele Bozzola):
kuibit 1.5.0 requires python 3.7 \(3.8.1 for developlment\) and works with any currently released version of Python
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: open
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
With 1.5 released should the version in ET be updated? What are minimum and maximum Python versions required?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…