We have several locations where we call pd.read_csv
locations throughout codebase at this time:
src/forest/jasmine/traj2stats.py:1859: df = pd.read_csv(file_path_array[i])
src/forest/oak/base.py:645: data = pd.concat([data, pd.read_csv(file_path)], axis=0) # read data
src/forest/poplar/legacy/common_funcs.py:175: identifiers = pd.read_csv(pathjoin(base_path, "identifiers", id_files[0]), sep=",")
src/forest/poplar/legacy/common_funcs.py:222: [pd.read_csv(pathjoin(datastream_path, the_csv)) for the_csv in files_in_range],
src/forest/sycamore/common.py:42: return pd.read_csv(filepath)
tests/conftest.py:67: data = pd.read_csv(pathjoin(TEST_DATA_DIR, "test_data_bout.csv"))
tutorials/forest_usage.ipynb:557: " temp_df = pd.read_csv(file_dir)\n",
tutorials/forest_usage.ipynb:629: " temp_df = pd.read_csv(file_dir)\n",
tutorials/forest_usage.ipynb:690: "response_data = pd.read_csv(path_resp)\n"
tutorials/helper_functions.py:87: temp_df = pd.read_csv(file_dir)
If we can unify all read-in code it can then be well factored, and we can provide guarantees, and over in Mano we well know exactly what normal use of forest expects and offer features
We have several locations where we call
pd.read_csvlocations throughout codebase at this time:
If we can unify all read-in code it can then be well factored, and we can provide guarantees, and over in Mano we well know exactly what normal use of forest expects and offer features