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
So i Have a relatively big context (8124 x 119). and it's in a Burmeister format.
it's taking forever to read it every time. what would be the fastest format to store such a context in for the purpose of a faster read ?
The text was updated successfully, but these errors were encountered:
I therefore suspect you are loading the data set using the GUI? I just tested it and can confirm that it takes about 30 seconds. However, most of the time is spent on rendering the data into the GUI. I am not sure if this can be remedied soon.
I too am experiencing a timeout issue when using the REST API context endpoint: REST-API#context-JSON. The problem seems to be that the length of the incidence data array grows very quickly.
To reproduce this problem, compare the internal read request with the API request. Consider the following two records. Firstly, seasoningplanner_de.cxt – a publicly accessible artificial data set. And secondly, clothing.cxt.txt (please rename to *.cxt), a more realistic dataset of the same size, but with denser incidence structures.
Reading the second data set via the REST-API-json endpoint will result in the following request text, which will result in a timeout exception. body.json
Uh oh!
There was an error while loading. Please reload this page.
So i Have a relatively big context (8124 x 119). and it's in a Burmeister format.
it's taking forever to read it every time. what would be the fastest format to store such a context in for the purpose of a faster read ?
The text was updated successfully, but these errors were encountered: