Update RegisterSlicesDeepSliceAbstractCommand.java

[PolarBean]

TAs discussed over email. to prepare for future versions of DeepSlice where these parameters will want to match the target atlas resolution.

[NicoKiaru]

Thanks! I think I will need to handle different versions and whether that run locally or remotely with the website.

A simple option is to let this parameter to the user and he has to deal with it. This has the advantage to be flexible. The alternative is to be clever... Is the update on the server already there ? Is the deepslice repo updated with it or will the new version be only available remotely ?

[PolarBean]

DeepSlice can handle any resolution so it won't affect it at the moment (no need for knowing which version is being used), I recommend lower res because otherwise it fills up the server too fast. I want to integrate user data into a future model and so if all user data at present is low resolution then I will be limited in what I can use. No worries if you want to keep it how it currently is!

[NicoKiaru]

Ok, now I get it. Two points on this:

• do you plan to support 16-bits (potentially multichannel) images or should the images be still 8-bit rgb ?
• do you plan to share at some point the data you collect ?

[PolarBean]

• No plans to support 16 bit
• No I won't share the data either as some people have expressed reservations on this. I will just use it to train new models and these will be released in the same manner as the existing ones.

[NicoKiaru]

Ok, then I think I need to spend a bit more time on a proper warning about the saturated images. The issue about white background images could be nice to tackle as well. I need to think about a convenient way for that.