FlightStream Scripting Spreadsheet Export Yields Wrong Binary Format
While writing some scripts for automating analysis, I have discovered that when I use the command:
"""EXPORT_SOLVER_ANALYSIS_SPREADSHEET
(path)"""
The resulting text file data is saved in UTF-8, but the file is encoded as UTF-16. This results in garbage data when opened by a standard text editor.
I can get around this by forcing reading in UTF-8, but this also results in a couple garbage characters.
This problem does not exist when I manually export the spreadsheet through the GUI. Is there another command I can enter to get the proper file format?
Best Answer
-
No worries! Thanks for checking that. We'll keep an eye on this issue. Hopefully we can find a solution so your workflow stays simpler.
0
Answers
-
The NUL characters in the output are commonly seen. I wouldn't worry about those.
The encoding does seem odd though. Are you running the script through the GUI or the terminal?
0 -
Hi Cory,
Sorry for the late reply. I just tested the script on both, and it does happen regardless of running through the GUI or the terminal.
It's not a big problem since I can always choose the alternate decoder, but it is sort of unusual.
Thanks,
Cooper
0 -
No worries! Thanks for checking that. We'll keep an eye on this issue. Hopefully we can find a solution so your workflow stays simpler.
0