Procedures for Procuring CASM for APT and RPS2 Releases Form of CASM Releases The Spike team will deliver the latest version of CASM for Linux, Solaris and Windows bundled in a zip file stored on the Solaris Science Cluster in the directory /data/software/build/casm/. The name of each delivered zip file should be unique to identify the corresponding version of CASM. This will make it easy for APT or RPS2 to revert to a previous version of CASM if the need arises. The bundled zip file will have the following directory structure: linux/LispPrograms/casm linux/LispPrograms/casm/casmfiles linux/LispPrograms/casm/casmfiles/casm-control linux/LispPrograms/casm/casmfiles/constraint-sets linux/LispPrograms/casm/casmfiles/moss macosx/LispPrograms/casm macosx/LispPrograms/casm/casmfiles macosx/LispPrograms/casm/casmfiles/casm-control macosx/LispPrograms/casm/casmfiles/constraint-sets macosx/LispPrograms/casm/casmfiles/moss solaris/LispPrograms/casm solaris/LispPrograms/casm/casmfiles solaris/LispPrograms/casm/casmfiles/casm-control solaris/LispPrograms/casm/casmfiles/constraint-sets solaris/LispPrograms/casm/casmfiles/moss windows/LispPrograms/casm windows/LispPrograms/casm/casmfiles windows/LispPrograms/casm/casmfiles/casm-control windows/LispPrograms/casm/casmfiles/constraint-sets windows/LispPrograms/casm/casmfiles/moss The casm software installation will be at the .../LispPrograms/casm directory level for each platform. CASM control files will be in the .../LispPrograms/casm/casmfiles/casm-control for each platform. The casm-control directory must include the visibility-table.vt file to facility running CASM with first running TRANS. The constraint sets file must be in the .../LispPrograms/casm/casmfiles/constraint-sets directory. Moving target files will be in the .../LispPrograms/casm/casmfiles/moss for each platform. CASM Releases New versions of the APT/RPS2 CASM zip file should be made with each new Spike release. Notification will be through the normal Spike release notifications sent to the spike-users email list. Note, that if particular changes to CASM pose a potential risk to proper operation of APT or RPS2, those changes should be limited to the CASM released around the time of the Phase I proposal deadline, usually in the mid-January time frame. This schedule allows sufficient time to test significant changes to CASM in the APT environment before the Phase II proposal preparation period. Ordinarily, the only changes of risk would be changes to external CASM interfaces.