Skip to content

Fixed --write_full_pae and --write_full_pde options. Fixes #585#602

Open
tomgoddard wants to merge 4 commits intojwohlwend:mainfrom
RBVI:pae_pde_fix
Open

Fixed --write_full_pae and --write_full_pde options. Fixes #585#602
tomgoddard wants to merge 4 commits intojwohlwend:mainfrom
RBVI:pae_pde_fix

Conversation

@tomgoddard
Copy link
Contributor

Implemented --write_full_pae and --write_full_pde options. Previously these options were available but ignored by the code and the PAE and PDE files were always written for boltz2 predictions, despite the documentation saying the default was false. Since the files have been written since boltz2 was released I made the default to write these files (ie. True). To not write them use --no_write_full_pae and --no_write_full_pde.

… Previously these options were available but ignored by the code and the PAE and PDE files were always written for boltz2 predictions. The documentation said the default was false. Since the files have been written since boltz2 was released I made the default to write these files (ie. True). To not write them use --no_write_full_pae and --no_write_full_pde.
@gcorso
Copy link
Collaborator

gcorso commented Oct 25, 2025

Thank you for pointing this out @tomgoddard ! Could you add a note about --no_write_full_pae/pde in the documentation table?

@tomgoddard
Copy link
Contributor Author

Ok, I added --no_write_full_pae and --no_write_full_pde to the documentation options table. Even though the default is true I left --write_full_pae and --write_full_pde in the options table since people may have been using that before and would be puzzled if it was not listed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants