Closed tcompa closed 2 years ago
Available options are: 'cyto', 'nuclei' and 'cyto2'. (anything else would not work)
This is now in-place (for both labeling tasks), to be tested.
In the example folders, one may add the "model_type"
key in the parameter file, as in
{
"workflow_name": "uzh_1_well_2x2_sites",
"dims": [2, 2],
"coarsening_xy": 2,
"coarsening_z": 1,
"num_levels": 5,
"channel_file": "../wf_params_uzh_cardiac_channels.json",
"path_dict_corr": "../wf_params_uzh_cardiac_illumination.json",
"image_labeling": {"coarsening_xy": 2, "labeling_level": 0, "labeling_channel": "A01_C01", "num_threads": 2, "relabeling": 1, "anisotropy": 6.1538, "diameter": 35.0, "cellprob_threshold": 0.0},
"image_labeling_whole_well": {"model_type": "cyto", "coarsening_xy": 2, "labeling_level": 2, "labeling_channel": "A01_C01", "diameter_level0": 35.0, "cellprob_threshold": 0.0,}
}
Just as a test, I ran a {1 well, 2x2 sites, 10 Z planes}
example with arbitrary model_type
's: cyto
for the per-FOV labeling, and cyto2
for the per-well labeling.
The runtime is a bit different than for nuclei
(it is actually a bit longer, in this case, with single FOVs labeled in about 10 minutes instead of about 4-5 minutes), but the run went through.
The output is reasonable (see two regions of the 3D and MIP labeling):
The feature is in-place and one example run went through, I'm closing this issue. Re-open if needed.