-
Notifications
You must be signed in to change notification settings - Fork 1
Ft/ensemble changes #115
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
base: main
Are you sure you want to change the base?
Ft/ensemble changes #115
Changes from all commits
27fa9c8
f64b650
0d4a3b6
9c1217d
0a12084
81c0bb3
a19a595
e93b3c1
70cb1af
942475d
de1cb95
819826c
59e52d4
cb7e65c
1b76b08
3e301f2
9545f4a
9c750ae
e79f9cc
ecf22ab
22c028c
19b67e8
4977d1e
8bd62ee
bcea5d0
f691a8b
4956fd4
4596949
44b4164
eeef708
f8962f8
37323c6
ee4b659
be7e494
eea6ea5
d598206
d14b22f
161c71b
9afda5d
72c0e90
34d81ba
01572d3
951abfb
720ddcf
b87bd57
7a3810a
90acab1
d64b908
c283d7a
00f1e39
fd2d622
00e98a0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,34 +1,36 @@ | ||
| # Ensemble experiment configuration | ||
| # This config can be used to run both the Ensemble attack training (``run_attack.py``) and testing phases (``tets_attack_model.py``). | ||
| base_experiment_dir: examples/ensemble_attack/tabddpm_20k_experiment_data # Processed data, and experiment artifacts will be stored here | ||
| base_data_config_dir: examples/ensemble_attack/data_configs # Training and data type configs are saved under this directory | ||
| # This config can be used to run both the Ensemble attack training (``run_attack.py``) and testing phases (``test_attack_model.py``). | ||
| base_experiment_dir: /projects/midst-experiments/ensemble_attack/tabddpm_10k_experiment_data/10k/ # Processed data, and experiment artifacts will be stored under this directory. | ||
| base_data_config_dir: examples/ensemble_attack/data_configs # Training and data type configs are saved under this directory. | ||
|
|
||
| # Pipeline control | ||
| # Training Pipeline Control | ||
| pipeline: | ||
| run_data_processing: true # Set this to false if you have already saved the processed data | ||
| run_shadow_model_training: true # Set this to false if shadow models are already trained and saved | ||
| run_metaclassifier_training: true | ||
|
|
||
| target_model: # This is only used for testing the attack on a real target model. | ||
| # This is for models trained on 20k data and generating 20k synthetic data | ||
| target_model_directory: /projects/midst-experiments/all_tabddpms/tabddpm_trained_with_20k/train/ | ||
| target_model_directory: /projects/midst-experiments/all_tabddpms/tabddpm_trained_with_10k/test/ | ||
| target_model_id: 21 # Will be overridden per SLURM array task | ||
| target_model_name: tabddpm_${target_model.target_model_id} | ||
| target_synthetic_data_path: ${target_model.target_model_directory}/${target_model.target_model_name}/synthetic_data/20k/20k.csv | ||
| target_synthetic_data_path: ${target_model.target_model_directory}/${target_model.target_model_name}/synthetic_data/10k/10k.csv | ||
| challenge_data_path: ${target_model.target_model_directory}/${target_model.target_model_name}/challenge_with_id.csv | ||
| challenge_label_path: ${target_model.target_model_directory}/${target_model.target_model_name}/challenge_label.csv | ||
|
|
||
| target_attack_artifact_dir: ${base_experiment_dir}/target_${target_model.target_model_id}_attack_artifacts/ | ||
emersodb marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| attack_probabilities_result_path: ${target_model.target_attack_artifact_dir}/attack_model_${target_model.target_model_id}_proba | ||
| target_shadow_models_output_path: ${target_model.target_attack_artifact_dir}/tabddpm_${target_model.target_model_id}_shadows_dir | ||
| target_shadow_models_output_path: ${base_experiment_dir}/test_all_targets # Sub-directory to store test shadows and results | ||
| attack_probabilities_result_path: ${target_model.target_shadow_models_output_path}/test_probabilities/attack_model_${target_model.target_model_id}_proba | ||
| attack_rmia_shadow_training_data_choice: "combined" # Options: "combined", "only_challenge", "only_train". This determines which data to use for training RMIA attack model in testing phase. | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a new config variable. You can read more about the options in
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe include something like |
||
| # See select_challenge_data_for_training()'s docstring for more details. | ||
|
|
||
|
|
||
| # Data paths | ||
| data_paths: | ||
| midst_data_path: /projects/midst-experiments/all_tabddpms # Used to collect the data | ||
| population_path: ${base_experiment_dir}/population_data # Path where the collected population data will be stored | ||
| processed_attack_data_path: ${base_experiment_dir}/attack_data # Path where the processed attack real train and evaluation data is stored | ||
| attack_evaluation_result_path: ${base_experiment_dir}/evaluation_results # Path where the attack evaluation results will be stored | ||
| midst_data_path: /projects/midst-experiments/all_tabddpms/ # Used to collect the data (input) as defined in data_processing_config | ||
| processed_base_data_dir: ${base_experiment_dir} # To save new processed data for training, or read from previously collected and processed data (testing phase). | ||
| population_path: ${data_paths.processed_base_data_dir}/population_data # Path where the collected population data will be stored (output/input) | ||
| processed_attack_data_path: ${data_paths.processed_base_data_dir}/attack_data # Path where the processed attack real train and evaluation data is stored (output/input) | ||
| attack_evaluation_result_path: ${base_experiment_dir}/evaluation_results # Path where the attack (train phase) evaluation results will be stored (output) | ||
|
|
||
|
|
||
| model_paths: | ||
| metaclassifier_model_path: ${base_experiment_dir}/trained_models # Path where the trained metaclassifier model will be saved | ||
|
|
@@ -38,23 +40,27 @@ model_paths: | |
| data_processing_config: | ||
| population_attack_data_types_to_collect: | ||
| [ | ||
| "tabddpm_trained_with_20k", | ||
| "tabddpm_trained_with_10k", | ||
| ] | ||
| challenge_attack_data_types_to_collect: | ||
| [ | ||
| "tabddpm_trained_with_20k", | ||
| "tabddpm_trained_with_10k", | ||
| ] | ||
| population_splits: ["train"] # Data splits to be collected for population data | ||
| challenge_splits: ["train"] # Data splits to be collected for challenge points | ||
| challenge_splits: ["train" , "test"] # Data splits to be collected for challenge points | ||
| original_population_data_path: /projects/midst-experiments/ensemble_attack/competition/population_data/ # This is where the original attack's population data (800k) will be read from, mainly to be used by DOMIAS | ||
| # You can download this data from https://github.com/CRCHUM-CITADEL/ensemble-mia/blob/main/input/population/population_all_with_challenge.csv | ||
|
|
||
| # The column name in the data to be used for stratified splitting. | ||
| column_to_stratify: "trans_type" # Attention: This value is not documented in the original codebase. | ||
| folder_ranges: #Specify folder ranges for any of the mentioned splits. | ||
| train: [[1, 20]] # Folders to be used for train data collection in the experiments | ||
| folder_ranges: # Specify folder ranges for any of the mentioned splits. | ||
| train: [[1, 21]] # Folders to be used for train data collection in the experiments | ||
| test: [[21, 31] , [31, 41]] | ||
| # File names in MIDST data directories. | ||
| single_table_train_data_file_name: "train_with_id.csv" | ||
| multi_table_train_data_file_name: "trans.csv" | ||
| challenge_data_file_name: "challenge_with_id.csv" | ||
| population_sample_size: 40000 # Population size is the total data that your attack has access to. | ||
| population_sample_size: 20000 # Population size is the total data that your attack has access to. | ||
| # In experiments, this is sampled out of all the collected training data in case the available data | ||
| # is more than this number. Note that, half of this data is actually used for training, the other half | ||
| # is used for evaluation. For example, with 40k population size, only 20k is used for training the attack model. | ||
|
|
@@ -86,7 +92,7 @@ shadow_training: | |
| fine_tune_diffusion_iterations: 200000 # Original code: 200000 | ||
| fine_tune_classifier_iterations: 20000 # Original code: 20000 | ||
| pre_train_data_size: 60000 # Original code: 60000 | ||
| number_of_points_to_synthesize: 20000 # Number of synthetic data samples to be generated by shadow models. | ||
| number_of_points_to_synthesize: 10000 # Number of synthetic data samples to be generated by shadow models. | ||
| # Original code: 20000 | ||
|
|
||
|
|
||
|
|
@@ -104,7 +110,7 @@ metaclassifier: | |
| meta_classifier_model_name: ${metaclassifier.model_type}_metaclassifier_model | ||
|
|
||
| attack_success_computation: | ||
| target_ids_to_test: [21,22,23] # List of target model IDs to compute the attack success for. | ||
| target_ids_to_test: [21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40] # List of target model IDs to compute the attack success for. | ||
|
|
||
| # General settings | ||
| random_seed: 42 # Set to null for no seed, or an integer for a fixed seed | ||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current single config is hard to understand because it mixes many variables and data paths with unclear names inherited from the original attack code. Splitting it into multiple pipeline‑specific configs would improve clarity and maintainability, even if it adds some overhead. Alternatively, improving variable naming within one config could be helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps (if you haven't already) you could create a clickup ticket with this in there as a next step?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think doing both (splitting and better naming) would be a worthwhile endeavor.