Closed matthewfeickert closed 2 years ago
@BenGalewsky can you remind me how the RIVER environment is actually setup with Conda? We have this documented on EXPANSE
but not RIVER and it would be good to make sure that the claim of
Remove the specifier on the cuda vs. nocuda jaxlib wheel as pip will be able to determine at install time what version can be installed.
actually holds up (though I think RIVER just has CPUs?)
(cc @alexander-held in case this is of interest)
Okay so as the Docker images deployed at RIVER are built on demand, c.f. https://github.com/matthewfeickert/distributed-inference-with-pyhf-and-funcX/issues/25#issuecomment-1106752153, then I think this is fine to merge. In the event that this becomes problematic for anyone I'm happy to revert quickly. :+1:
Update the version of JAX used to support a larger range of CPythons. Remove the specifier on the cuda vs. nocuda jaxlib wheel as pip will be able to determine at install time what version can be installed. This also will allow for nocuda versions to be installed on macOS machines that want to replicate the environment locally.
e.g. from https://storage.googleapis.com/jax-releases/jax_releases.html for
jaxlib
v0.3.7
there iswhile for
jaxlib
v0.1.66
there was only Linux wheelsSquash and merge commit message