• The code which makes the R0+ release has been tagged with the CVS tag: ALMA-R0+. If you are interested in the souces, you can retrieve them with:

•  It is important that from now on everybody has the possibility to compile and run his/her software against the complete ALMA software, not only the ACS. This is the quickest way to discover problems (like possible conflicts among files and so on).
• A binary distribution of the complete ALMA SW is available on the web, in the IT&S pages under the link "Download" and it is called ACSSW.tar.gz. (For the moment, we use the same name that can be accessed through the environment variable $ACSROOT).The download is password protected. Send a mail to alma-sw-it@nrao.edu to know the authentication information.
• You should untar the file under your /alma/ACS-2.1 directory after saving the actual ACSSW. If you find any problem, you will be able to quickly switch back to the previous working situation.
• From now on, the integrated ALMA SW will be distributed in the same way after every monthly integration. It is important that you install it on your machine!

• No compilation problems; the guards in most of the idl files have been correctly implemented. Few files still don't have them:

   

  ./ACS_SRC/ACS/LGPL/CommonSoftware/XmlIdl/idl/xmltest.idl
  ./ACS_SRC/ACS/LGPL/CommonSoftware/jcontnc/idl/javaNCTestComp.idl
  ./ACS_SRC/ACS/LGPL/acsBUILD/config/Doxyfile.idl
  ./PIPELINE_SRC/PIPELINE/Science/idl/junk/ExampleSciencePipeline.idl
  ./PIPELINE_SRC/PIPELINE/Science/idl/junk/NprotoSciencePipeline.idl
  ./PIPELINE_SRC/PIPELINE/Science/idl/junk/ProtoSciencePipeline.idl
  ./PIPELINE_SRC/PIPELINE/Science/idl/junk/SimpleSciencePipeline.idl
  ./PIPELINE_SRC/PIPELINE/Science/idl/junk/XprotoSciencePipeline.idl

A part from javaNCTestComp.idl, probably the others are not used at all; we'd like to receive a confirmation from the responsible persons for those files, though.

• The test code developed by each Subsystem is quite below our ideal internal threshold of 50% on the entire written code

• The preparation of integration tests is progressing and received some improvements with R0+. The deadline for having a complete system test is R1. As soon a repeatable structure is ready we'll open a section in our IT&S pages .
• Running the integration tests, we found a non-blocking problem with IFR and some idl files. The problem is at the moment still under investigation by G. Chiozzi and B. Jeram. As soon as we have more information we'll let you know.

• starting from this integration, we publish some results prepared by M. Zamparelli using software quality tools and different metrics. For the moment, a static analysis only is available. In the future dynamic analysis also on the code should be performed. Please, be reminded that these results are run on the software delivered for the monthly integration using the monthly cvs tag. They can differ from the analogous pages prepared by Michele every night using the HEAD of the code in CVS. The results are available here.

• source code

• test code