I think I can justify this being on the Thylacine side.
In order to use the Bilby model, you have to supply two parameters:
--dll-dir points to the directory that holds the Glider DLLs, including WallabyHAL.dll and any others that the system needs to run (which may be all of them), as well as pyglider.pyd. This is canonically x64/Debug (or possibly Release) under the HAL build dir.
--config-dir points to the directory that holds the various csv files used to configure the system. Typically, this will be WallabyHAL under the build dir.
What I'd like to do is to right a standalone Python script (in dev-tools) that can be run on a system that's built Glider and pulls all the necessary files into a single zip file that can be handed to a user. The user can then just extract everything into a single directory, point both args at that directory and run everything.
Migrated from internal repository. Originally created by @EvanKirshenbaum on Jul 28, 2023 at 11:23 PM PDT.
I think I can justify this being on the Thylacine side.
In order to use the Bilby model, you have to supply two parameters:
--dll-dir
points to the directory that holds the Glider DLLs, includingWallabyHAL.dll
and any others that the system needs to run (which may be all of them), as well aspyglider.pyd
. This is canonicallyx64/Debug
(or possiblyRelease
) under the HAL build dir.--config-dir
points to the directory that holds the variouscsv
files used to configure the system. Typically, this will beWallabyHAL
under the build dir.What I'd like to do is to right a standalone Python script (in
dev-tools
) that can be run on a system that's built Glider and pulls all the necessary files into a single zip file that can be handed to a user. The user can then just extract everything into a single directory, point both args at that directory and run everything.Migrated from internal repository. Originally created by @EvanKirshenbaum on Jul 28, 2023 at 11:23 PM PDT.