PEPS Software - Revision history

PepsUser at 03:29, 26 May 2026

2026-05-26T03:29:01Z

← Older revision		Revision as of 03:29, 26 May 2026
Line 37:		Line 37:
	# An account at [https://gitlab.iap.kit.edu https://gitlab.iap.kit.edu]		# An account at [https://gitlab.iap.kit.edu https://gitlab.iap.kit.edu]
	# Configure your account to have ssh keys for cloning. Provides a much more efficient workflow, using git over ssh and not https.		# Configure your account to have ssh keys for cloning. Provides a much more efficient workflow, using git over ssh and not https.


	~~=== Slide ===~~

	* [[media:detector-etc-2026-05-25.pdf Detector and event data structures]]

	You then run		You then run

2026-05-26T03:25:35Z

@@ Line 37: / Line 37: @@
 # An account at [https://gitlab.iap.kit.edu https://gitlab.iap.kit.edu]
 # Configure your account to have ssh keys for cloning. Provides a much more efficient workflow, using git over ssh and not https.
 You then run
@@ Line 85: / Line 90: @@
 You are now ready to run any of the validations, standard applications, and examples.

2026-05-26T01:37:05Z

← Older revision		Revision as of 01:37, 26 May 2026
Line 42:		Line 42:
	git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps		git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps

	to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch. This step takes some time due to the size of the repository.		to clone the repository into the ''offline-peps' directory and switch to the ''peps' branch. This step takes some time due to the size of the repository.

2026-05-26T00:38:23Z

← Older revision		Revision as of 00:38, 26 May 2026
Line 71:		Line 71:

	ctest --test-dir ../offline-peps-build -j 32		ctest --test-dir ../offline-peps-build -j 32


			=== Activate and use the offline software ===

			You have to set up the environment for the offline software using

			eval $(../offline-peps-install/bin/auger-offline-config --env-sh)

			You find validation test in the ''ValidationTests''. We also have example applications and Tutorials:

			➤ ls ../offline-peps-install/share/auger-offline/doc
			ADST ExampleApplications SampleShowers StandardApplications Tutorials UserSkeleton

			You are now ready to run any of the validations, standard applications, and examples.

2026-05-26T00:30:33Z

Configure and build

← Older revision		Revision as of 00:30, 26 May 2026
Line 63:		Line 63:

	cmake --build ../offline-peps-build		cmake --build ../offline-peps-build

			and install

			cmake --build ../offline-peps-build -t install

			You run the unit tests using

			ctest --test-dir ../offline-peps-build -j 32

2026-05-26T00:27:37Z

← Older revision		Revision as of 00:27, 26 May 2026
Line 43:		Line 43:

	to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch. This step takes some time due to the size of the repository.		to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch. This step takes some time due to the size of the repository.


			=== Configure and build ===

			The software is configured using, for example,

			cmake -S . -B ../offline-peps-build -GNinja -Dprefix=../offline-peps-install -DAUGER_TESTING_ENABLED=ON -DDBHOST=db.auger.unam.mx

			The last three parameters are optional:

			; -GNinja
			: Use ''ninja'' to build. It is about 20% faster than ''make''.
			; -DAUGER_TESTING_ENABLED=ON
			: Build unit tests
			; -DDBHOST=db.auger.unam.mx
			: Use the UNAM DB server for Auger.

			You can now build using

			cmake --build ../offline-peps-build

2026-05-26T00:11:32Z

Getting externals: ape

← Older revision		Revision as of 00:11, 26 May 2026
Line 27:		Line 27:
	and go for a coffee (depends on your machine). To use the installed package, you have to set up the required environment variables using		and go for a coffee (depends on your machine). To use the installed package, you have to set up the required environment variables using

	eval $(./ape ~~env-~~sh externals)		eval $(./ape sh externals)

	'''Note:''' we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).		'''Note:''' we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).

2026-05-26T00:10:06Z

Getting externals: ape

← Older revision		Revision as of 00:10, 26 May 2026
Line 25:		Line 25:
	./ape install externals		./ape install externals

	and go for a coffee (depends on your machine).		and go for a coffee (depends on your machine). To use the installed package, you have to set up the required environment variables using

			eval $(./ape env-sh externals)

	'''Note:''' we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).		'''Note:''' we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).


	=== Getting offline from gitlab ===		=== Getting offline from gitlab ===

2026-05-26T00:08:06Z

Getting offline from gitlab

← Older revision		Revision as of 00:08, 26 May 2026
Line 41:		Line 41:
	git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps		git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps

	to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch.		to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch. This step takes some time due to the size of the repository.

2026-05-26T00:06:12Z

← Older revision		Revision as of 00:06, 26 May 2026
Line 28:		Line 28:

	'''Note:''' we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).		'''Note:''' we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).


			=== Getting offline from gitlab ===

			The Auger Offline software is available from the [https://gitlab.iap.kit.edu/auger-observatory/offline/offline offline project] at the IAP-KIT gitlab server. You need

			# An account at [https://gitlab.iap.kit.edu https://gitlab.iap.kit.edu]
			# Configure your account to have ssh keys for cloning. Provides a much more efficient workflow, using git over ssh and not https.

			You then run

			git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps

			to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch.