I made the effort of test-reading from the two files as well. Perhaps the data was shifted a bit - thus this tells us nothing.ĭoes someone have an idea what is going on here? Is the appended file using a much more optimized data-structure perhaps? Or maybe windows has cached the file and makes access to it much faster? And a test with fc in windows 7 revealed. '-struct stu_data2disk ', temp_str_blockName, ' '.Īnd again the file saves nicely (286MB). Thus instead of the above I loop over the blocks and append them in sequence: OK - then I remembered that I would like to follow the save-procedure over the 40 blocks. The file is written without problems (286MB). Save converted.mat -struct stu_data2disk -v7.3 Now I would like to save the data using one of two possible methods. I now have all my random test-data in a struct stu_data2disk. Stu_data2disk.(sprintf('block_%03u', num_k)) = temp_stu_value % generate temp struct for current block: Temp_str_blockName = sprintf('block_%03u', num_k)
#MATLAB 2009 OPEN VARIABLES CODE#
I then generate some dummy code that has shape and size identical to the actual raw data: Which is why I am concerned with the following.Īnyway, first I define some general variables: Remark: In the real script (that I have yet to finish) I will be doing the above at total of 370 times, converting a total of 108GB of raw data. Field frames contains a 480x240圆5 sequence of uint8 imagedata (here just random data generated using randi). Each variable will be named "block_NNN" from 1 to 40 and will contain a struct with fields frames and blockNo. mat-file will contain 40 blocks as individual variables. In this current test-scenario I will be generating one output: A -v7.3 mat-file. My question is more in the sense: Why am I observing the following surprising (for me) behavior in MATLAB? My files saves nicely using the save command. zip files to v7.3 mat files (with an underlying HDF5-datamodel). I am using MATLAB R2009b and I need to write a larger script that converts the contents of a larger set of.
#MATLAB 2009 OPEN VARIABLES UPDATE#
As per the update below from July 2016, the issue/bug in MATLAB seems to no longer exist (tested with R2016a scroll down to end of question to see update). NOTE: This question deals with an issue observed back in 2011 with an old MATLAB version (R2009a).