Deafult loader is used when you simply pass the file name.
You can use .label.nii.gz extension instead of just .nii.gz as a hint to get your volume loaded as labelmap (or .seg.nrrd to make it load as a segmentation).
If renaming the file is impossible then you can force reading as volume+labelmap by calling Slicer.exe --python-code "slicer.util.loadVolume('/tmp/series/T1.nii.gz'); slicer.util.loadLabelVolume('/tmp/series/Mask.nii.gz')" or as volume+segmentation by by calling Slicer.exe --python-code "slicer.util.loadVolume('/tmp/series/T1.nii.gz'); seg=slicer.util.loadSegmentation('/tmp/series/Mask.nii.gz'); seg.CreateClosedSurfaceRepresentation()".
Segmentation has many advantages over simple labelmaps, for example, it is rendered in slice views a bit nicer (it shows a stronger outline and more transparent filling) it can be easily displayed in 3D view, you can sort&filter segments, associate with standard terminologies, etc.
That’s right, Slicer something.seg.nrrd is loaded properly as segmentation but something.label.nrrd is still loaded as scalar volume (if you drag-and-drop something.label.nrrd then by default it is loaded as labelmap, but not when passing as command-line argument).
I’ll add .label.nii.gz and .label.nrrd as recognized composite file extensions to Slicer Preview Release, but until then you can use --python-code argument to force loading any volume as labelmap (regardless of filename extension).
You can change labelmap display node properties to set region outline/filling, but I would recommend to load labelmap volumes as segmentation instead (due to the advantages described above).
It would be easy to add outline/fill as an option to setSliceViewerLayers (pull requests are welcome), which would simplify the startup script. You can also add utility function like slicer.show('somevolume.nrrd','somelabel.nrrd') to your .slicerrc.py file or in an extension.
However, labelmap volumes are becoming more and more used just as legacy infrastructure, so I would recommend to load them as segmentation (slicer.util.loadSegmentation('somelabel.nrrd')).
Related to this command I would like to ask something…
As you mention I am able to run my image and corresponding a segmentation file from terminal but I would like to ask How can I run same image with 2 diiferent corresponding segmentation files? Is it possible?