The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Why is
Best Answer
-
jacobcybulski Member, University Professor Posts: 391 UnicornMake sure that your first row are column names (it is also possible in one of the steps to define the first row as comment and then the second as column titles). Because your first row were numbers, the import wizard assumed that you have no column names and treated them as nominal values. This resulted in chaos later on. So delete the first row of numbers and make the column names as row one. Also some of your column names may be illegal in RM, e. g. remove special characters from column names, ideally use only characters and underscores. After those changes the CSV will read in.
5
Answers
Oddly RM doesn't even pull in Row 1 (SMA and EMA etc variables like 20 day or 50 day EMAverage) on this import, yet still "calls them out" as being errors?
Would it be better if I just deleted Row 1 and its variables?
I'd already decided to delete Row 1 and rename anything that looked similar.
"format your dates as proper date strings"
I think this is currently the best format dd/mm/yyyy.... but then I found about a years worth of dates with a different format so that was converted.
Then it showed I had commas on the Open data (Dow Jones), so I deleted those, then it found more in another column and another...
so eventually I selected every relevant column and formatted the whole workbook and then it imported fine.
Cheers again Jacob.