>>> Integration Status >>>
		Development Area e.g. $CVSROOT/offline/hft/ or private directories	Official Area $CVSROOT/
PXL
StRoot/	StPxlClusterMaker/	Review complete	Deployed
	StPxlDbMaker/	Review complete	Deployed
	StPxlHitMaker/	Review complete	Deployed
	StPxlMonMaker/ StPxlQAMaker/	Under review. Non critical for production chain
	StPxlRawHitMaker/	Review complete	Deployed
	StPxlSimMaker/	Review complete	Deployed
	StPxlUtil/	Review complete	Deployed
	StEvent/	XXX: List individual files for clarity	Deployed. May benefit from changes as for IST. For example, there are constants defined multiple times
	StiPxl/		Deployed but still may benefit from a review
StarDb/Geometry/pxl/		Currently we use the local tables in this directory. Not clear if we can run without them. Need to understand what is available in the official STAR DB tables
IST
StRoot/	StIstCalibrationMaker/	To be reviewed. Non critical for production chain
	StIstClusterMaker/	Review complete	Deployed
	StIstDbMaker/	Review complete	Deployed
	StIstFastSimMaker/	To be reviewed. Non critical for production chain
	StIstHitMaker/	To be reviewed
	StIstQAMaker/	To be reviewed. Non critical for production chain. Should it be renamed to StIstMonMaker similar to StPxlMonMaker?
	StIstRawHitMaker/	Review complete	Deployed
	StIstUtil/	Review complete	Deployed
	StEvent/	Reviewed by Thomas. XXX: List individual files for clarity. There seems to be an issue with StIstFastSimMaker that depends on StEvent	Deployed
	StiIst		Deployed but still may benefit from a review
StarDb/Geometry/ist		Currently we use the local tables in this directory. Not clear if we can run without them. Need to understand what is available in the official STAR DB tables
SSD
StRoot/	StSsdClusterMaker/		Empty module. The code is in StSsdPointMaker/
	StSsdDaqMaker/		Expect new code in StSstDaqMaker/
	StSsdDbMaker/		Reuse existing code
	StSsdMonMaker/	Updates available in Jonathan's private directory	Updated existing module with SST related code
	StSsdEvalMaker/		Empty module. Apparently not used
	StSsdFastSimMaker/		Reuse existing code
	StSsdPointMaker/	Updates available in Jonathan's private directory	Updated existing module with SST related code
	StSsdSimulationMaker/		Reuse existing code
	StSsdUtil/		Reuse existing code
	StSstDaqMaker/	Peer review in progress...
	StiSsd		Updated existing module with SST related code
StarDb/Geometry/ssd/			Directory exists but the content is ~3 years old

	— Implementation stage
	— Review stage
	— Code can be moved to $CVSROOT
	— Ready for extensive testing with production libraries

- Double counting of density in energy loss fixed

- Not accurate acount  of energy loss in gas and in parent node fixed

- Energy loss calculator created authomatically inside of material. No need to do it by hands now

- Saving of energy loss data in node for following analisys

- Methods to calculate weight and volume size of detectors implemented. Using this a lot of discrepances were found btween TGeo weight and Sti weight of detectors

- Automatic splitting of average volumes (planar & cylindrical) implemented

- Removing not needed detector is added. Used in StiIst. Average volume created and then more precize volume made, using info of average one. Then average deleted

- Test angle for new hit 33=>55 . In result of HFT alignement, hits are so far from origine volume, that old test is too strict. When some alignement of volumes will be added, probably this problem will disappeared

- It was found, that track crossing of cylinder is not accurate enough. Rewritten.

- In method setLayerRadius, tolerance  added, to avoid two objects  with slightly different  layer radius to be in dofferent layers

- Function recov(), which recovers bad error matrix (non positive)   rewritten and simplified.

- In new, more complicated geometry, it became possible that track in local coordinate system has cos(Phi) negative. It leads to negative path in energy loss calculation and as a result wrong error matriix. Found and fixed

- Tonight, Sep 23 I commit a bug 2917: TGeoPhisical volume has different weight then TGeoVolume. Our average  Sti volumes created from TGeoPhysicalVolume and hence could be wrong