[MINC-users] Reading time-width data with minc2 API

[Claude LEPAGE]

Jim,

>   Done.  malloc is commented out and 3.1415 is indeed returned.

Great! we know this function works now.

> Hmmm .... don't think so.  When I look at the header, the "time" and
> "time-width" variables are designated as "irregular".  Note the
> attributes and the actual data values:
> --------------------------------------
>         double time(time) ;
>                 time:length = 34 ;
>                 time:dimorder = "time" ;
>                 time:varid = "MINC standard variable" ;
>                 time:vartype = "dimension____" ;
>                 time:version = "MINC Version    1.0" ;
>                 time:spacing = "irregular" ;
>                 time:alignment = "start_" ;
>                 time:units = "seconds" ;
>                 time:start = 0.016 ;
>                 time:step = 145.454545454545 ;
>         double time-width(time) ;
>                 time-width:dimorder = "time" ;
>                 time-width:varid = "MINC standard variable" ;
>                 time-width:vartype = "dim-width____" ;
>                 time-width:version = "MINC Version    1.0" ;
>                 time-width:spacing = "irregular" ;
>                 time-width:filtertype = "square____" ;
>                 time-width:units = "seconds" ;
>
>  time = 0.016, 15.016, 30.016, 45.016, 60.016, 90.016, 120.016, 150.016,
>     180.016, 210.016, 240.016, 270.016, 300.016, 360.016, 420.016, 480.016,
>     540.016, 600.016, 660.016, 720.016, 780.016, 840.016, 1020.016, 1200.016,
>     1500.016, 1800.016, 2100.016, 2400.016, 2700.016, 3000.016, 3300.016,
>     3600.016, 4200.016, 4800.016 ;
>  time-width = 15, 15, 15, 15, 30, 30, 30, 30, 30, 30, 30, 30, 60, 60, 60, 60,
>     60, 60, 60, 60, 60, 180, 180, 300, 300, 300, 300, 300, 300, 300, 300,
>     600, 600, 600 ;

Now we have to figure out why the time intervals are not being read properly.
Sounds like fun. Maybe Andrew wants to jump on the bandwagon...

Claude