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 guess this comes a bit late, but I just realized that the format of the input files is somewhat problematic.
The additional white space is nice for readability in small example files but of no great use in larger files which aren't read by humans anyways.
The issue with the whitespace is that it causes unnecessarily large file sizes and consequentially also longer than necessary read-in times!
Both file size and read-in times can be reduced significantly (70-80%) by using input files for which all whitespace is removed.
The following script provides one way to accomplish this:
For people using standard json parser there will be no problem. But we don't know if it is the case for every body, we'll see during the semi-finale evaluation.
I guess this comes a bit late, but I just realized that the format of the input files is somewhat problematic.
The additional white space is nice for readability in small example files but of no great use in larger files which aren't read by humans anyways.
The issue with the whitespace is that it causes unnecessarily large file sizes and consequentially also longer than necessary read-in times!
Both file size and read-in times can be reduced significantly (70-80%) by using input files for which all whitespace is removed.
The following script provides one way to accomplish this:
e.g. with
I feel that it would be in everyone's interest, if you'd run the evaluation with the reduced-size input files.
Kind regards
Marco
The text was updated successfully, but these errors were encountered: