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
If you follow the instructions in setup, you will end up with two directories, "data" and "code". The data needed for the lesson are of course in the "data" directory. However in the lesson, it is assumed that your code is in the same directory as the data, you are using. This is of course possible, but working on code in the "data" directory seems counterintuitive. Either the lessons should be changed to include the path to the data directory, or the strange choice of working directory should be addressed during presentation.
The text was updated successfully, but these errors were encountered:
This is a great consideration! Spending some time teaching workshop attendees about paths is an essential skill in my opinion. Usually, it is best to have your code in your project folder and then your data in a "data" folder in the same folder. That way all your paths to your data will be ./data/datafile.csv. For anyone interested in ideal data organization strategies for scientific computing, I would recommend two papers written by Greg Wilson: Best Practices for Scientific Computing Good enough practices in scientific computing
It's a bit confusing that the 'code' directory is not referred to in the lesson material until the very last episode (which many instructors may not get to).
another enhancement would be to have both directories contained within the same zip file.
If you follow the instructions in setup, you will end up with two directories, "data" and "code". The data needed for the lesson are of course in the "data" directory. However in the lesson, it is assumed that your code is in the same directory as the data, you are using. This is of course possible, but working on code in the "data" directory seems counterintuitive. Either the lessons should be changed to include the path to the data directory, or the strange choice of working directory should be addressed during presentation.
The text was updated successfully, but these errors were encountered: