September 26, 2017 at 8:27 pm
Comments posted to this topic are about the item Reading a CSV
September 27, 2017 at 12:06 am
Only ever worked with a SQL data set, so learned something new, thanks Steve
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
September 27, 2017 at 1:21 am
Subtle difference between third and fourth options caught me out.
September 27, 2017 at 7:08 am
The use of backslashes in file addressing is very well explained e.g. in R for Microsoft Excel Users
Easier is to use forward slashes: file="c:/nfl/2016qbstats.csv"
September 27, 2017 at 7:33 am
It's a bit of an easy question, it would have been a bit, harder if it had escaped \ in one of the red herrings. As it stands, if one knows that a \ in a quoted filename has to be escaped that takes you immediately to the right answer without having to know anything about read.csv or the inability to copye from a file without calling a function to do it or the nonexistence of loadcsv (or maybe it exists in some obscure package somewhere?).
Tom
September 27, 2017 at 7:50 am
Forward slash is easier. We can use the singlequote as well for the file path parameter
September 27, 2017 at 7:51 pm
It is nice to see A NFL-related question that does not assume that you know the rules. Thanks, Steve!
September 28, 2017 at 6:49 am
Revenant - Wednesday, September 27, 2017 7:51 PMIt is nice to see A NFL-related question that does not assume that you know the rules. Thanks, Steve!
I didn't even realized that it was an NFL related question. Only after I saw your comment and went back to find out that it had QB stats for last season.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy