nanli-emory

Hi @choosehappy I need help opening the issue link from http://hawking.case.edu:3000/issues/197. Could you provide me with more information about this one?

Hi @choosehappy, since we will use the image thumbnail and it should be not huge in pixels so I will use iterate each channel and find the ranges for each...

> Almost there. Can the seed parameter be located at the top of the file to indicate it is applied globally (to all modules)? Do you mean on top of...

> Looks like there is no such thing as a global config parameter, since each module is only passed the parameters from it's section: > > https://github.com/choosehappy/HistoQC/blob/3653ffb50a4a17c44fd5daacd357ddd4227e8884/histoqc/_pipeline.py#L365 > > ```python...

> I guess my question is - why do we need to pass this variable around? Once the seed is set at application launch -- all subsequent modules should become...

> > > in the end, we should be using a default seed, with the option to change it on the command line, so that things are both "automatically" reproducible,...

Hi @choosehappy, @jacksonjacobs1 and @CielAl, Currently, I moved the **seed** as optional arguments in command line and the **default value is None** https://github.com/nanli-emory/HistoQC/blob/12dca26383b5b826e683027b91d80d880eaf7cee/histoqc/__main__.py#L57 As you see, I passed the **seed**...

> Revisiting this issue now. > > I agree that the seed should be set in the _shared_state dict. > > @nanli-emory Is there anything that still needs to be...

Hi @OmarAshkar, could you provide more information about your run environments such as the version of OS, python, and docker? what GPUs do you use? It will help us to...