transonic issueshttps://foss.heptapod.net/fluiddyn/transonic/-/issues2020-02-12T22:35:12Zhttps://foss.heptapod.net/fluiddyn/transonic/-/issues/7Detect unsupported assignment self.attr = 12020-02-12T22:35:12ZBitbucket ImporterDetect unsupported assignment self.attr = 1*Created originally on Bitbucket by [paugier (Pierre Augier)](https://bitbucket.org/%7Beb327c54-cadd-4fce-9edd-f8fe047a9b93%7D/)*
*Created originally on Bitbucket by [paugier (Pierre Augier)](https://bitbucket.org/%7Beb327c54-cadd-4fce-9edd-f8fe047a9b93%7D/)*
https://foss.heptapod.net/fluiddyn/transonic/-/issues/5Transonic jit compilation+mpi blocks simulations2020-02-12T22:35:11ZBitbucket ImporterTransonic jit compilation+mpi blocks simulations*Created originally on Bitbucket by [avmo (Ashwin Vishnu)](https://bitbucket.org/%7Bbd72905e-cf99-4847-84c2-998104370f6e%7D/)*
## Issue
Simulations are frozen if attempted to launch with MPI from a fresh installation of `fluidsim`.
...*Created originally on Bitbucket by [avmo (Ashwin Vishnu)](https://bitbucket.org/%7Bbd72905e-cf99-4847-84c2-998104370f6e%7D/)*
## Issue
Simulations are frozen if attempted to launch with MPI from a fresh installation of `fluidsim`.
## Reproduce
* make a fresh virtualenv with the following requirements:
```
Cython==0.29.4
decorator==4.3.2
gast==0.2.2
mpi4py==3.0.0
networkx==2.2
numpy==1.16.1
ply==3.11
pythran==0.9.1.post0
six==1.12.0
```
```pip install -r requirements.txt```
* Install `fluidfft` and `fluiddyn` using `make develop` from the respective repos.
* Clear cache:
```sh
TRANSONIC_DIR=$FLUIDSIM_PATH/.transonic transonic -cc fluidsim.solvers.sw1l
```
* Run a set of tests with mpi and jit compilation
```sh
TRANSONIC_COMPILE_JIT=1 mpirun -n 2 fluidsim-test -m fluidsim.solvers.sw1l
```https://foss.heptapod.net/fluiddyn/transonic/-/issues/2HPC related qustions on fresh install and JIT compilation on jobs2020-02-12T22:35:08ZBitbucket ImporterHPC related qustions on fresh install and JIT compilation on jobs*Created originally on Bitbucket by [avmo (Ashwin Vishnu)](https://bitbucket.org/%7Bbd72905e-cf99-4847-84c2-998104370f6e%7D/)*
Some of my jobs were frozen during JIT compilation, and it was never released, even after 24 hrs. It was prob...*Created originally on Bitbucket by [avmo (Ashwin Vishnu)](https://bitbucket.org/%7Bbd72905e-cf99-4847-84c2-998104370f6e%7D/)*
Some of my jobs were frozen during JIT compilation, and it was never released, even after 24 hrs. It was probably because I had the environment variable `OMP_NUM_THREADS=1` on. Nevertheless, would it be possible to check if the threads are released after JIT compilation is done.