🚀 go-pugleaf

In article <1993Jan25.211337.5466@news.dfrf.nasa.gov> Todd Vernon,
todd@fred.dfrf.nasa.gov writes:
>Our site uses Matlab 3.0 and now is moving to 4.0.  We have
>a few CMEX programs we generated to load large files containing
>time history data sets. 
>
>Due to the way Matlab handles CMEX interaction, ( all passed 
>back data must be in a left hand argument),  this makes it
>very difficult to load data sets with unknown number or
>matrices.
>
>Our data is mostly vector data, so what we do is pass back
>2 left hand args, one that contains all our 1-by-n vectors 
>packed into one matrix, and the other a matrix of characters
>that make up each vector name.  After words, we have a m-file
>that breaks apart each seperate vector putting it in a matlab
>variable by the name in the other matix.  What a PAIN.  
>
>Are we missing something here.   We really need a way to create
>matrices as we load the data and not have our hands tied by
>having to pass them back through left hand args.  
>
>This really hinders our ability to access the data we need to 
>get to, any suggestions.  Changing data format is NOT an option.
>
>Thanks in advance.


The MEX-file facility in MATLAB 4.0 includes a new routine called
mexPutMatrix that allows you to plop a matrix directly back into 
the MATLAB workspace.


John Little