Closed ErinWeisbart closed 1 year ago
And by forever it seems like maybe quite literally forever - I left it for hours and it never solved.
So in 5467aa3867343f5c058d1824f48fcb1f2a57d635 I did my best to clean it up into something that solves quickly. Following various troubleshooting guides, I:
Will run all the notebooks with this environment to ensure that I didn't accidentally remove something necessary and/or that bumping versions doesn't affect results.
Major caveat that this is out of my area of expertise, so will be good to have folks weigh in on this and let me know if it should be handled differently.
Looking right now, but I don't think you committed that file
Partly this may be because I'm on an M1, but conda-forge said it wouldn't give me python 3.7.1 (or 3.7 at all)
Updating 3 lines got a working environment in my hands -
Here's the diff
@@ -2,14 +2,14 @@ name: periscope_2022
dependencies:
-- conda-forge::python=3.7.1
+- conda-forge::python=3.8
-- conda-forge::ipykernel=5.1.0
-- conda-forge::nb_conda_kernels=2.2.1
+- conda-forge::ipykernel=5
+- conda-forge::nb_conda_kernels
Here's the full enviroment
Caveat here - I came at this from the opposite angle you did, "minimal changes to working product", as opposed to "minimum code required for functional product". Yours is MUCH better - we definitely want to drop things we aren't using.
Sorry, linked the wrong commit. Updated it in comment above.
Can we clean up the conda environment? Creating the environment currently takes forever...
@bethac07 Is this something you can help with when you get the chance?