Analysis codes - Revision history

Copp at 16:47, October 14, 2021

2021-10-14T16:47:05Z

← Older revision		Revision as of 16:47, October 14, 2021
Line 1:		Line 1:
	== Typical run procedure ==		== Typical run procedure ==
			''Original content prior to the 2021 Gammasphere Upgrade Project.''

	Traditionally you will have a directory structure as		Traditionally you will have a directory structure as
Line 172:		Line 173:

	''Go back to [[Digital Gammasphere Upgrade Project]]''		''Go back to [[Digital Gammasphere Upgrade Project]]''

			''Go back to [[ANL GEBSort and Analysis Codes]]''

Copp at 14:21, October 5, 2021

2021-10-05T14:21:21Z

← Older revision		Revision as of 14:21, October 5, 2021
Line 170:		Line 170:

	'''The energy processing in bin_dgs follows algorithms that were developed by Shoufei Zhu.'''		'''The energy processing in bin_dgs follows algorithms that were developed by Shoufei Zhu.'''

			''Go back to [[Digital Gammasphere Upgrade Project]]''

Tlauritsen at 22:06, January 22, 2020

2020-01-22T22:06:47Z

← Older revision		Revision as of 22:06, January 22, 2020
Line 38:		Line 38:
	(cd GEBSort; make -B)		(cd GEBSort; make -B)
	git clone https://gitlab.phy.anl.gov/tlauritsen/gtreceiver.git		git clone https://gitlab.phy.anl.gov/tlauritsen/gtreceiver.git
	(cd ~~GEBSort~~; make -B)		(cd gtreceiver; make -B)

	Where, of course, for DGS you do not need the tracking part. It is only shown for completeness		Where, of course, for DGS you do not need the tracking part. It is only shown for completeness

Tlauritsen at 19:20, August 14, 2019

2019-08-14T19:20:20Z

← Older revision		Revision as of 19:20, August 14, 2019
Line 42:		Line 42:
	Where, of course, for DGS you do not need the tracking part. It is only shown for completeness		Where, of course, for DGS you do not need the tracking part. It is only shown for completeness

	= ~~acquire~~ and sort data =		= Acquire and sort data =

	To acquire the data, cd to the 'data' directory.		To acquire the data, cd to the 'data' directory.

Tlauritsen at 16:53, August 14, 2019

2019-08-14T16:53:55Z

← Older revision		Revision as of 16:53, August 14, 2019
Line 142:		Line 142:
	After you executed dgs_pz, a d_pz.cmd file was generated. Use that cmd file in gf3 to check the pz spectra. Some might be really bad and dgs_pz might not have been able to find a good PZ value. If that is the case, to get around this problem, you may set the PZ for these detectors to the average value of the ones that had good PZ spectra. You would simply edit the dgs_pz.cal file.		After you executed dgs_pz, a d_pz.cmd file was generated. Use that cmd file in gf3 to check the pz spectra. Some might be really bad and dgs_pz might not have been able to find a good PZ value. If that is the case, to get around this problem, you may set the PZ for these detectors to the average value of the ones that had good PZ spectra. You would simply edit the dgs_pz.cal file.

	Now, after the PZ file is generated,		Now, after the PZ calibration file is generated,

	run GEBSort again		run GEBSort again
Line 163:		Line 163:
	Next when you run GEBSort_nogeb, both the new PZ values in dgs_pz.cal and the gain and offset values in dgs_ehi.cal are read in and used.		Next when you run GEBSort_nogeb, both the new PZ values in dgs_pz.cal and the gain and offset values in dgs_ehi.cal are read in and used.
	Take a good look at the spectra. Sometimes the dgs_pz and dgs_ecal programs can be fooled by noise or strange features in the spectra, so a few PZ and ecal parameters might have to be specified by hand.		Take a good look at the spectra. Sometimes the dgs_pz and dgs_ecal programs can be fooled by noise or strange features in the spectra, so a few PZ and ecal parameters might have to be specified by hand.

			To extract the calibrated spectra

			.x get_ecln.cc


	'''The energy processing in bin_dgs follows algorithms that were developed by Shoufei Zhu.'''		'''The energy processing in bin_dgs follows algorithms that were developed by Shoufei Zhu.'''

Tlauritsen at 16:48, August 14, 2019

2019-08-14T16:48:52Z

← Older revision		Revision as of 16:48, August 14, 2019
Line 119:		Line 119:
	dgs_pz 350 141 dgs_pz.cal 1.003		dgs_pz 350 141 dgs_pz.cal 1.003

	where 350 141 are the M and K values you find in the runxx.save file. Specify the values in 10 nsec units. In this case I saw these lines in the run_xxx.save or run_xxx.info file:		where 350 141 are the M and K values you find in the runxx.save or runxx.info file. Specify the values in 10 nsec units. In this case I saw these lines in the run_xxx.save or run_xxx.info file:

	GLBL:DIG:d_window 0.06		GLBL:DIG:d_window 0.06
Line 142:		Line 142:
	After you executed dgs_pz, a d_pz.cmd file was generated. Use that cmd file in gf3 to check the pz spectra. Some might be really bad and dgs_pz might not have been able to find a good PZ value. If that is the case, to get around this problem, you may set the PZ for these detectors to the average value of the ones that had good PZ spectra. You would simply edit the dgs_pz.cal file.		After you executed dgs_pz, a d_pz.cmd file was generated. Use that cmd file in gf3 to check the pz spectra. Some might be really bad and dgs_pz might not have been able to find a good PZ value. If that is the case, to get around this problem, you may set the PZ for these detectors to the average value of the ones that had good PZ spectra. You would simply edit the dgs_pz.cal file.

	Now, after the PZ file is generated, ~~remove the energy calibration file if there is one:~~		Now, after the PZ file is generated,

	~~rm dgs_ehi.cal~~		run GEBSort again

	~~so that the calibrations defaults to 0 and 1 for offset and gain and sort again~~
	~~using the new pz values that were extracted above.~~
	When you resort, the PZ values in dgs_pz.cal are read in and used.		When you resort, the PZ values in dgs_pz.cal are read in and used.
	Extract the new clean, uncalibrated, ehi spectra as		Extract the new clean, uncalibrated, ehi spectra as

	.x ~~get_ecln~~.cc		.x get_eraw.cc

	and run the calibration program (you may have to compile)		and run the calibration program (you may have to compile)

Tlauritsen at 23:15, August 13, 2019

2019-08-13T23:15:05Z

← Older revision		Revision as of 23:15, August 13, 2019
Line 156:		Line 156:

	dgs_ecal dgs_ehi.cal 207Bi 600 1.0		dgs_ecal dgs_ehi.cal 207Bi 600 1.0
			or
			dgs_ecal2 dgs_ehi.cal 207Bi 600 1.0

	you can also use "88Y", "60Co" for the source. The calibration in this case will be 1.0keV/ch (last argument).		you can also use "88Y", "60Co" for the source. The calibration in this case will be 1.0keV/ch (last argument).
	The last parameter specifies the lowest channel the program will search for peaks in to avoid any noise at low energies.		The last parameter specifies the lowest channel the program will search for peaks in to avoid any noise at low energies.
			dgs_ecal2 has been developed lately and may be better at handling difficult peaks. Feel fre to try this new version.

	Next when you run GEBSort_nogeb, both the new PZ values in dgs_pz.cal and the gain and offset values in dgs_ehi.cal are read in and used.		Next when you run GEBSort_nogeb, both the new PZ values in dgs_pz.cal and the gain and offset values in dgs_ehi.cal are read in and used.

Tlauritsen at 11:44, August 13, 2019

2019-08-13T11:44:20Z

← Older revision		Revision as of 11:44, August 13, 2019
Line 40:		Line 40:
	(cd GEBSort; make -B)		(cd GEBSort; make -B)

	Where, of course, for DGS you do not need the tracking part.		Where, of course, for DGS you do not need the tracking part. It is only shown for completeness

	= acquire and sort data =		= acquire and sort data =
Line 135:		Line 135:
	the GLBL: lines in the listing. THIS NEEDS TO BE CONFIRMED.		the GLBL: lines in the listing. THIS NEEDS TO BE CONFIRMED.

	~~On less you know what you are doing, do~~ not execute the caput commands		Do not execute the caput commands in the .save file. For the
	in the .save file.		purpose here, the lines are just information.

	you already specified the M value in GEBSort.chat		you already specified the M value in GEBSort.chat

Tlauritsen at 11:41, August 13, 2019

2019-08-13T11:41:29Z

← Older revision		Revision as of 11:41, August 13, 2019
Line 133:		Line 133:

	Only the GLOBAL m, k and d values matter. Thus, just look at		Only the GLOBAL m, k and d values matter. Thus, just look at
	the GLBL: lines in the listing		the GLBL: lines in the listing. THIS NEEDS TO BE CONFIRMED.

			On less you know what you are doing, do not execute the caput commands
			in the .save file.

	you already specified the M value in GEBSort.chat		you already specified the M value in GEBSort.chat

Tlauritsen at 11:36, August 13, 2019

2019-08-13T11:36:55Z

← Older revision		Revision as of 11:36, August 13, 2019
Line 119:		Line 119:
	dgs_pz 350 141 dgs_pz.cal 1.003		dgs_pz 350 141 dgs_pz.cal 1.003

	where 350 141 are the M and K values you find in the runxx.save file. Specify the values in 10 nsec units. In this case I saw these lines in the run_xxx.save file:		where 350 141 are the M and K values you find in the runxx.save file. Specify the values in 10 nsec units. In this case I saw these lines in the run_xxx.save or run_xxx.info file:

	GLBL:DIG:d_window 0.06		GLBL:DIG:d_window 0.06