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
Not sure whether to call this a bug or not. We used to ingest dakota_tabular.dat files without modification. Now it fails with the error "Error setting-up local connection: Could not parse file dakota_tabular.dat". The parsing error comes from the fact that dakota_tabular.dat files have an odd format whereby all the rows, except the first header row, start with spaces (spaces are also used as the delimiting characters). Given that this is not a well formed a delimited text file, in some ways it is not a bug. But if people are using Slycat with Dakota, it is a problem to manually repair each file. The repair is to remove the initial spaces from the start of each row.
The text was updated successfully, but these errors were encountered:
Not sure whether to call this a bug or not. We used to ingest dakota_tabular.dat files without modification. Now it fails with the error "Error setting-up local connection: Could not parse file dakota_tabular.dat". The parsing error comes from the fact that dakota_tabular.dat files have an odd format whereby all the rows, except the first header row, start with spaces (spaces are also used as the delimiting characters). Given that this is not a well formed a delimited text file, in some ways it is not a bug. But if people are using Slycat with Dakota, it is a problem to manually repair each file. The repair is to remove the initial spaces from the start of each row.
The text was updated successfully, but these errors were encountered: