But when I try to access the data of these variables, only the first one, var_x->data, is accessible. The other pointers indicate:
"data 0x00000000 void*" in the watch.
Is there a way I can do this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is nothing wrong with what you typed and I regularly load multiple variables at once. Make sure the MAT file has all of those variables and they are not empty. Also, make sure that you execute those lines in the debugger. Sometimes with optimizations it is not clear if lines have executed or not. Empty variables may have a data pointer of NULL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-16
Hi! Thanks for the fast response.
I'm sorry, but there must be something wrong. Even if I code like this:
Only var_x->data is a valid pointer. The others are 0x00000000. I ran those lines in the debugger. As the variables are 88 million sized double arrays, it takes a while when I run the first line, but the other two execute really fast.
The mat file version is 4 and I run in VisualStudio 2012, I don't know if that helps.
I noticed that after I use Mat_VarRead a first time, the next times will have variables with invalid values as *data.
Please, is there any way I can work this around?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can acces the data pointer of both variables "x" and "y" in matlab. But I really need to have access to both of them at the same time, because I proccess them at the same time in a very long loop. And the only way to read both is doing as I mentioned above.
Could it be a problem in version 1.5.0?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-19
Hi.
This discussion can be closed. I figured out that the 3rd variable wasn't getting its value simply because it was exceeding the max memory available for the proccess.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
what is actually the maximum number of rows and columns that can be put in the array? Is it dependent on the system resources, or is there also a techinical limitation?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi! First I'd like to thank for this great project.
I'm currently trying to read many variables at once, so I can use them in the rest of my code, like this:
But when I try to access the data of these variables, only the first one, var_x->data, is accessible. The other pointers indicate:
"data 0x00000000 void*" in the watch.
Is there a way I can do this?
There is nothing wrong with what you typed and I regularly load multiple variables at once. Make sure the MAT file has all of those variables and they are not empty. Also, make sure that you execute those lines in the debugger. Sometimes with optimizations it is not clear if lines have executed or not. Empty variables may have a data pointer of NULL.
Hi! Thanks for the fast response.
I'm sorry, but there must be something wrong. Even if I code like this:
Only var_x->data is a valid pointer. The others are 0x00000000. I ran those lines in the debugger. As the variables are 88 million sized double arrays, it takes a while when I run the first line, but the other two execute really fast.
The mat file version is 4 and I run in VisualStudio 2012, I don't know if that helps.
I noticed that after I use Mat_VarRead a first time, the next times will have variables with invalid values as *data.
Please, is there any way I can work this around?
Ok, i noticed that if I do the following:
I can acces the data pointer of both variables "x" and "y" in matlab. But I really need to have access to both of them at the same time, because I proccess them at the same time in a very long loop. And the only way to read both is doing as I mentioned above.
Could it be a problem in version 1.5.0?
Hi.
This discussion can be closed. I figured out that the 3rd variable wasn't getting its value simply because it was exceeding the max memory available for the proccess.
Thanks!
what is actually the maximum number of rows and columns that can be put in the array? Is it dependent on the system resources, or is there also a techinical limitation?