Skip to content

Clarification on --pretrained usage (for fine-tuning?) and possible parser issue #11

@eleproia

Description

@eleproia

Dear all,

First of all, congratulations on this repository — great work!

We would like to fine-tune GEMS on proprietary crystal structures, starting from an already trained GEMS checkpoint and using it as a pretrained model.

While looking into train.py, we had a couple of questions regarding the --pretrained argument:

  1. Is using the --pretrained flag to load a model checkpoint and train the model with additional crystal structures the intended and correct way to use this option?

  2. We noticed that the argument parser currently defines

parser.add_argument(
    "--pretrained",
    default=False,
    type=lambda x: x.lower() in ['true', '1', 'yes'],  
    help="Provide the path of a state dict that should be imported"
)

However, this seems to cast the argument to a boolean, while the help string (and the code below) suggests that a string path to a checkpoint should be provided.
Would it be more appropriate for --pretrained to be of type str, so that it can directly accept the path to the model checkpoint?

Thank you very much for your time and for maintaining this project.

Best regards,
Eleonora

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions