This PR adds a 4th step in colabdesign tool to visualise the checkpoint pdbs.
These images will also now be available in the raw_files tab. The visualizer has 2 modes. When GPU is found, it uses a powerful render engine called CYCLES, and with GPU acceleration, it takes about 15 seconds to create 1 image. When GPU is not present, this engine takes 10x more time, so in those cases, there's a fallback logic to use BLENDER_EEVEE render engine, which creates a lesser quality image in CPU around the same time mark. The example below shows 2 images, left with GPU + CYCLES and the right one with CPU + BLENDER_EEVEE
Steps to Test
A successful test will show x number of png images in the raw_files tab, equal to the number of binders in the input. These images should also match the pdbs visualised in the checkpoint area.
If you want to test locally with test.sh script, removing the --gpus=all flag from the docker run command should result in the fallback and usage of BLENDER_EEVEE render engine.
What type of PR is this?
Description
This PR adds a 4th step in colabdesign tool to visualise the checkpoint pdbs. These images will also now be available in the raw_files tab. The visualizer has 2 modes. When GPU is found, it uses a powerful render engine called CYCLES, and with GPU acceleration, it takes about 15 seconds to create 1 image. When GPU is not present, this engine takes 10x more time, so in those cases, there's a fallback logic to use BLENDER_EEVEE render engine, which creates a lesser quality image in CPU around the same time mark. The example below shows 2 images, left with GPU + CYCLES and the right one with CPU + BLENDER_EEVEE
Steps to Test
A successful test will show x number of png images in the raw_files tab, equal to the number of binders in the input. These images should also match the pdbs visualised in the checkpoint area.
If you want to test locally with test.sh script, removing the
--gpus=all
flag from the docker run command should result in the fallback and usage of BLENDER_EEVEE render engine.