From discussion with @qiencai @radka-j @ContiPaolo, a useful extension would be to implement support for masks.
This might be in a few different contexts:
- Fixed mask (both at training and inference time, e.g. a land mass)
- In this case it could be passed upon initialization of the model and used in the loss and forward calculations
- Unknown mask at inference time (e.g. acoustic scattering - maze in The Well)
- In this case the specific mask would need to be passed at inference time
- We might look to extend the
Batch API to have a field called mask and this could be populated/derived from a given constant field already present or some additional data
Two example papers on this:
Other thoughts:
- If we can identify API that can be flexible and minimise repeated implementation would be great.
- API to support mask concatenation as a new channel might be worthwhile.
- An outstanding question is how to handle masking that works in the latent space too.
From discussion with @qiencai @radka-j @ContiPaolo, a useful extension would be to implement support for masks.
This might be in a few different contexts:
BatchAPI to have a field calledmaskand this could be populated/derived from a given constant field already present or some additional dataTwo example papers on this:
Other thoughts: