Hi! We currently need to submit a singularity container for evaluation on the VOT2022 sequestered dataset, but because the VOT toolkit will write the track results in the file system during evaluation and analysis, and the sif container is a read-only system, so the sif container maybe cannot be used for run.
The official documentation of the singularity container says that the read-only sif container needs to be converted to a sandbox writable container.
We found that using the singularity command:
singularity build --sandbox --fakeroot xxx/ xxx.sif
To convert the sif container into a writable sanbox can run normally. Does the official approve this submission method?
By the way, does the submission of VOT2022 in the sequestered dataset need to submit the sif container? Or def definition files as well as source code? Because the capacity of the sif container is relatively large, it may not be submitted by email. Is it allowed to provide a Google drive link.
Hi! We currently need to submit a singularity container for evaluation on the VOT2022 sequestered dataset, but because the VOT toolkit will write the track results in the file system during evaluation and analysis, and the sif container is a read-only system, so the sif container maybe cannot be used for run. The official documentation of the singularity container says that the read-only sif container needs to be converted to a sandbox writable container. We found that using the singularity command:
singularity build --sandbox --fakeroot xxx/ xxx.sifTo convert the sif container into a writable sanbox can run normally. Does the official approve this submission method? By the way, does the submission of VOT2022 in the sequestered dataset need to submit the sif container? Or def definition files as well as source code? Because the capacity of the sif container is relatively large, it may not be submitted by email. Is it allowed to provide a Google drive link.