Checkpoints for Unet3D not being on the storage system>

[FileSystemGuy]

We have passed the deadline for new issues to be created against your submission, so this "issue" is for informational purposes only, it will not force a rerun of your submission. In fact the deadline for submitting reruns is today, and since there has been no communications from the peer review committee of the Storage WG that you need to do a rerun, nothing is required of you.

We are curious if it was an oversight to not put the checkpoints folder location onto the storage system under test? In CLOSED submissions, that is a requirement, but it is not a requirement for OPEN submissions.

We are trying to tease out what you were intending to show off in your OPEN submission that made you decide it could not be a CLOSED submission.

[leoyanghw]

1. Yes, having the checkpoint folders on the host storage was an oversight. We used the default setting for the checkpoint folder location.

2. Because we added a new run_benchmark.sh script to the benchmark directory, we considered this to be a change to the benchmark code. That’s the reason why we submitted it in the open division.