Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose additional configuration options #131

Closed
bfclarke opened this issue Aug 28, 2024 · 0 comments · Fixed by #138
Closed

Expose additional configuration options #131

bfclarke opened this issue Aug 28, 2024 · 0 comments · Fixed by #138
Assignees
Labels
enhancement New feature or request

Comments

@bfclarke
Copy link
Contributor

There are configuration options hard-coded in deeprvat/deeprvat/base_configurations.yaml that are currently not supported in deeprvat_input_config.yaml but should be exposed (with current hard-coded values as defaults):

#DeepRVAT model training settings
training:
    train_proportion: 0.8
    n_parallel_jobs: 6
    dataloader_config:
        batch_size: 1024
        num_workers: 0
        temp_dir: $TMPDIR/deeprvat_train

#DeepRVAT model settings
model:
    type: DeepSet
    config:
        phi_layers: 2
        phi_hidden_dim: 20
        rho_layers: 3
        rho_hidden_dim: 10
        activation: LeakyReLU
        pool: max
        use_sigmoid: True
        metrics:
            objective: MSE
            objective_mode: min
            loss: MSE
            all:
                MSE: {}
                PearsonCorrTorch: {}
                MAE: {}
                RSquared: {}
        optimizer:
            type: AdamW
            config: {}

#Training dataset settings
training_data:
    dataloader_config:
        batch_size: 64
        num_workers: 8

#Association dataset settings
association_testing_data:
    dataloader_config:
        batch_size: 16
        num_workers: 10

#Additional settings for association testing
n_burden_chunks: 5
n_regression_chunks: 2
n_avg_chunks: 1
@bfclarke bfclarke added the enhancement New feature or request label Aug 28, 2024
@meyerkm meyerkm self-assigned this Sep 10, 2024
@meyerkm meyerkm linked a pull request Sep 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants