Move nested CV into a separate file #4
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've exported the nested CV to a separate file, but I'm not entirely satisfied with the current structure. The process involves first manipulating the data in the notebook, saving it as a pickle, then running a separate script, and finally bringing the results back to this notebook. Do you think it would be better to have the data processing as a separate script?
Additionally, I've been struggling to calculate memory usage, so I could not do it. About the timing, right now, I'm tracking the time for each model within the outer loop. So, if we have, let's say, 100 iterations, we end up with separate entries in the results dictionary for each model and dataset (including taxonomic levels). However, I'm wondering if it would be more appropriate to have a cumulative time for each model type instead. For example, all the Random Forests together. What do you think?