Kalum Ost

Update on this, now that we have implicit time profiling; this error seems to incur a 20s cost on the first run of DeepSeg as well. You can see it...

I actually was going to do this as part of a broader rewrite of the argument parser, in preparation to solve #4801. Will take a while though (lots of technical...

So, before I start implementing this in any capacity, I wanted to run the proposed changes to ensure their aren't any major objections to anything: **New `logging` Utility** Primarily used...

> Does this imply a global logger + logging state? If so, then one caveat to keep in mind is the leaking of state when one CLI script calls another....

I don't mind a tedium task to whittle away at between other complex projects, honestly; just means it will take a while to shift the corresponding PR out of draft...

Necro-posting a bit to discuss this: > I think using containers wouldn't really help, here. The reason Compute Canada doesn't want us to install Conda, and the reason they provide...

Draft PR #4857 has an implementation of this now; I tested and confirmed it works on Calgary's HPC, just waiting to get 2FA set up for Alliance Canada to confirm...

> I made a diff of the passing vs. failing runs, and the installed packages are exactly the same: https://www.diffchecker.com/qQ0fJGUT/ > > My hunch is that perhaps there is some...

Has their been any progress on this? If not, I think we should kick it down the road to SCT 7.1, as testing this kind of thing is probably going...

Spinning this up initially as a draft PR so that GitHub can run the tests for me; avoids setting my laptop on fire.