problem with regressOut
Closed this issue · 1 comments
schmucr1 commented
on the new cluster we experience that the regressOut step in the standard worfklow is very slow when run in an interactive jupyterlab session launched via the shpc portal. we do not understand whether the problem is related to besca, to the regressOut function or its package version, or to jupyterlab. but it seems that this occurs only in sessions launched via the shpc portal.
it would be good if we could investigate this issue and find a solution.
i started to explore with public data stored under this path /scratch/site/u/schmucr1/test_regressOut/
i can help with this issue.