[MINC-users] RGB volumes and register

[Andrew Janke]

Thanks,

I'll take a crack at building it from source.


a


On 22 July 2016 at 22:31, Robert D. Vincent <robert.d.vincent at mcgill.ca> wrote:
> Hi,
>
> I accidentally disabled the RGB volume handling in volume_io a while ago,
> then fixed it when it was reported. The current develop branch should work
> as always.
>
> See
> https://github.com/BIC-MNI/libminc/commit/a1839e0d717f38e4bf1839a35a151796935d3b03
>
> The actual test for RGB volumes starts at line 175 of input_mnc.c in the
> current develop branch. The vector_dimension needs to be the final
> dimension in the file and should be of length 3, generally. I don't think
> the voxel type matters.
>
>     -bert
>
> On Thu, Jul 21, 2016 at 11:26 PM, Andrew Janke <a.janke at gmail.com> wrote:
>
>> Probably for Bert,
>>
>> Can anyone comment on how the current version of register in
>> minc-toolkit-v2 determines if a volume is RGB or not? It doens't seem
>> to be based upon dimension order as per previous versions.
>>
>> This bit of old Dave McDonald code would insinuate that the volume has
>> to be an unsigned long?
>>
>>
>> https://github.com/BIC-MNI/libminc/blob/develop/volume_io/Volumes/volumes.c#L568
>>
>> Which is called deep within register:
>>
>>
>> https://github.com/BIC-MNI/Register/search?utf8=%E2%9C%93&q=is_an_rgb_volume
>>
>> ?
>>
>> So, the question remains, what dimension order, dimensions and
>> datatype should I use? Previously this was
>> vector_dimension,zspace,yspace,xspace + unsigned byte (0-255).
>>
>> ta
>>
>>
>> a
>> _______________________________________________
>> MINC-users at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>>
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users