A toolset to work with modular genotype databases formatted using Poseidon. The main executable within this package is called trident.

Detailed user documentation can be found on our website.

To install the development version of poseidon-hs/trident you can follow these steps:

1. Install the Haskell build tool Stack
2. Clone this repository
3. Execute stack install inside the repository to build the tool and copy the executables to ~/.local/bin (which you may want to add to your path). This will install the compiler and all dependencies into folders that won't interfere with any installation you might already have.
4. To run the tests, execute stack test inside the repository to build and run tests.

The technical haddock documentation for the poseidon-hs Haskell library is available here (you can also render it locally using stack haddock and open it subsequently using stack haddock --open). The critical package is the Poseidon.Package module which defines the core functions to read and work with module files.

Important packages to look into to understand the architecture of this tool:

• Start with Poseidon.Package: It defines the main package format and provides some functions how to access the data inside packages.
• The Poseidon.Utils module only provides the definition of an Exception type.
• The modules in CLI/ define the functionality provided in the command line functions for trident.
• The list command might be a good place to start understanding what's going on and how to use the Poseidon.Package interface.

The Github Actions script in .github/workflows/release.yml registers a new draft release and automatically builds and uploads trident binaries when a new Git tag with the prefix v* is pushed.

# locally register a new tag (e.g. 0.3.1)
git tag -a v0.3.1 -m "see CHANGELOG.md"
# push tag
git push origin v0.3.1

In case of a failing build delete the tag and the release draft on Github and then delete the tag locally with

git tag -d v0.3.1

before rerunning the procedure above.

To test some of the output of the powerful trident CLI functions, poseidon-hs features a golden test mechanism:

The output of a number of CLI function calls implemented in test/Poseidon/GoldenTestsRunCommands.hs is stored in a static file storage (test/testDat/poseidonHSGoldenTestData), together with relevant checksums for these files in test/testDat/poseidonHSGoldenTestCheckSumFile.txt.

stack test then runs -- among other things -- the code in /test/testDat/poseidonHSGoldenTestData again and stores the result in a dynamic, temporary directory. It then validates the output by comparing the new and temporary checksums with the old and git-logged checksums in said file poseidonHSGoldenTestCheckSumFile.txt. Any deviation between these two sets of checksums will cause the test to fail. The test output in this case will therefore only print the name of the operation or the output file that changed, not what exactly changed within this file.

To find out what exactly changed and also update the output storage and static checksum file, you can run poseidon-devtools updateGoldenTests and compare the old and new static output storage with git diff.