Details
-
Type:
Improvement
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
-
Team:Architecture
Description
https://pipelines.lsst.io/install/newinstall.html gives instructions on how to install the stack, and
https://pipelines.lsst.io/install/newinstall.html#newinstall-other-tags gives instructions on how to install a specific release.
It would be useful to clarify in the "run newinstall.sh" step on that page that the version of the newinstall you download and run needs to be consistent with the version of eups install distrib that you will run later, and to mention the difference in tagging conventions (w.2021.15 v w_2021_15). As it is now, that information isn't mentioned until a side note in the "install science pipeline packages" section which refers to the "#newinstall-other-tags" label. This could be as simple as putting a reference to the #newinstall-other-tags at the start of the "run newinstall.sh" step. This will avoid newbies having to rerun newinstall.sh once they realize it isn't consistent with the version of the stack they want.
It would also be useful to collect any other tips that the folks are using in practice, such as cloning the environment (is that the envars or the conda environment btw?), or somehow collecting the PYTHONPATH from eups for tools like visual studio and to point people at those.
Kian-Tat Lim I've added this to Architecture for now.