You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to read from MLJ ResultsTables using Java API and I get weird errors, having to do with the fact that the Label ColumnIndex is -1. Basically I don't manage to read the correct numbers from the table using Java. Interestingly, when I save the table once to disc and read it again it works.
I realized the following:
The table on the right comes directly from MLJ and it is missing the RowNumberColumn (without heading), which all the other tables have. I suspect that maybe this causes the errors. Could you maybe have a look at your code to see what the difference is to, e.g. AnalyzeParticles? My current feeling is that the MLJ ResultsTables are in some way having a defect...at least, as said, I don't manage the properly read the numbers from them using the Java API.
The text was updated successfully, but these errors were encountered:
Hello @iarganda @dlegland @imagejan
I am trying to read from MLJ ResultsTables using Java API and I get weird errors, having to do with the fact that the
Label
ColumnIndex is-1
. Basically I don't manage to read the correct numbers from the table using Java. Interestingly, when I save the table once to disc and read it again it works.I realized the following:
![image](https://user-images.githubusercontent.com/2157566/52524393-bbdf3a80-2c9c-11e9-8ef0-544b16142145.png)
The table on the right comes directly from MLJ and it is missing the
RowNumberColumn
(without heading), which all the other tables have. I suspect that maybe this causes the errors. Could you maybe have a look at your code to see what the difference is to, e.g. AnalyzeParticles? My current feeling is that the MLJResultsTables
are in some way having a defect...at least, as said, I don't manage the properly read the numbers from them using the Java API.The text was updated successfully, but these errors were encountered: