release 0.7
-
features -
doc -
update CHANGELOG -
update icons in orangeonctrib -
test -
test memory leak from slurm + random data generator I haven't saw anything on this. Maybe not tested with the "good" workflow. Some memory cleanup could be done once in the datavalidator / datalist. But this is more on cleaning dark / ref this shouldn't "overload" lbs191. - workflow A (auto or manual): nxtomomill -> data selector -> darkref -> axis -> saaxis -> nabu (several pag) -> data viewer
-
AlFoam60kev -
bamboo_hercules -
bassanite (zseries) -
S03_16N_5S_0p67_L1_0p182
-
-
-
test installation from pip install tomwer[full] -
package -
installation on slurm, lbs... -
prepare venv in lbs -
prepare venv ubuntu20_pow9 -
prepare venv ubuntu20_x86_64 -
prepare venv deb8_x86_64 -
prepare venv deb9_x86_64 -
create a script to connect directly to the appropriate venv as nabu usage is: source /scisoft/tomotools_env/tomwer/activate.sh {version}
. Example:source /scisoft/tomotools_env/tomwer/activate.sh 0.7
-
update nabu once released
-
-
integrate modifications on master branch