Data Processing

For data processing details, please refer to RGBW Joint Remosaic and Denoise dataset.

Data Download

The training data contains 70 pairs of input RGBW and output bayer raw data. Both RGBW input and ground truth bayer are of the same spatial resolution: 1200x1800, and they are of 10bits in the .bin format. The validation and testing set has 15 scenes each. For each scene in the training, validation and testing dataset, we have three noise levels: 0dB, 24dB and 42dB, and therefore the total number of images is 210, 45 and 45 for training, validation and testing dataset. The input images from the validation and testing set are provided but the GT are not available to participants.

Dataset splitNoise levelInputOutput bayer (to submit)ID# of images
train 0dB rgbw_xxx_fullres_0db.bin rgbw_xxx_fullres_0db.bin 001-070 70
train 24dB rgbw_xxx_fullres_24db.bin rgbw_xxx_fullres_24db.bin 001-070 70
train 42dB rgbw_xxx_fullres_42db.bin rgbw_xxx_fullres_42db.bin 001-070 70
validation 0dB rgbw_xxx_fullres_0db.bin rgbw_xxx_fullres_0db.bin 071-085 15
validation 24dB rgbw_xxx_fullres_24db.bin rgbw_xxx_fullres_24db.bin 071-085 15
validation 42dB rgbw_xxx_fullres_42db.bin rgbw_xxx_fullres_42db.bin 071-085 15
test 0dB rgbw_xxx_fullres_0db.bin rgbw_xxx_fullres_0db.bin 086-100 15
test 24dB rgbw_xxx_fullres_24db.bin rgbw_xxx_fullres_24db.bin 086-100 15
test 42dB rgbw_xxx_fullres_42db.bin rgbw_xxx_fullres_42db.bin 086-100 15

More details can be found in the README.md in rgbw_rmsc_start_here.zip in the training dataset.

Submission

For submitting the results, you need to follow these steps:

  1. Process the input images and keep the same name for the output image results as produced by your method (example: for an input file with name "001.bin" the output file should also be "001.bin") 
  2. The input images for both the validation and test datasets have three different noise levels. Therefore, the total number of images to submit is 45 for the validation and test dataset respectively.
  3. The readme.txt file should contain the following lines filled in with the runtime per image (in seconds) of the solution.
    Runtime per image [s] : 0.10 
    Other description : GPU: Titan Xp;  
    The last part of the file can have any description you want about the code producing the provided results (dependencies, link, scripts, etc.). The provided information is very important both during the validation period when different teams can compare their results / solutions but also for establishing the final ranking of the teams and their methods.
  4. Create a ZIP archive containing all the output image results named as above and a readme.txt. Note that the archive should not include folders, all the images/files should be in the root of the archive.

Note that the submission score shown on "Submit/View Results" tab is not the final ranking. See the evaluation page for our weighted metric for the final score.

We recommend you use our [scoring program] to check your submission is correct.

Final Submission

Participants will need to submit results on Codalab server. The submission format is the same as the validation phase's.

Apart from submission on Codalab server, all participants should email to the challenge organizer mipi.challenge@gmail.com to complete the final submission.

The subject of the email should be: RGBW Joint Remosaic and Denoise MIPI-Challenge - TEAM_NAME

The body of the mail shall include the following information:
a) the challenge name
b) team name
c) team leader's name and email address
d) rest of the team members
e) team name and user names on CodaLab competitions
f) executable/source code attached or download links
g) Each team in the final testing phase should write up a factsheet to describe their solution(s) [factsheet template]
h) download link to the results of all of the test frames

Note that the executable/source code should include pre-trained models or necessary parameters so that we could run it and reproduce results. There should be a README or descriptions that explain how to execute the executable/code. Factsheet must be a compiled pdf file. Please provide a detailed explanation.