Cli.081 - Ted Wong prepared dataset for long term climate projections for two states in India by bkrram · Pull Request #303 · resource-watch/data-pre-processing

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

bkrram · 2025-02-03T06:40:11Z

Checklist for Reviewing a Pre-Processing Script

Does the python script contain the following 4 sections: Download data and save to your data directory, Process data, Upload processed data to Carto/Upload processed data to Google Earth Engine, Upload original data and processed data to Amazon S3 storage?
[ x] Does the script have the standardized variable names for: dataset_name, raw_data_file, processed_data_file?
[ x] Does the script create and use a 'data' directory?
[ x] Does the script use a python module to automatically download the data? If this is not possible, are there explicit instructions for how to download the data (step by step with instructions about every input parameter and button to click to find the exact data) and does it use shutil to move the data from 'Downloads' into the data directory?
[ x] Is the script automated as much as possible to minimize rewriting code the next time the dataset updates (ex 1: can you automatically pull out column names instead of typing them yourself? ex 2: if you are dropping columns with no data, did you use pandas to find the nodata columns instead of dropping the column by name?)
[ x] Are there comments on almost every line of code to explicitly state what is being done and why?
[ x] Are you uploading to the correct AWS location?
[ x] For GEE scripts, did you explicitly define the band manifest with a pyramiding policy so that we can easily change it later if we need to?
[ x] Does the README contain all relevant links?
[ x] Does the README state the original file type?
Does the README list all of the processing steps that were taken in the script?
For netcdfs, does the README state which variables were pulled from the netcdf?
[ x] Did you use the util functions whenever possible?
Have you checked the processed data file on your computer to make sure it matches the data you uploaded to Carto? (spaces or symbol names in column titles often get changed in the upload process-please change these before uploading so that the backed up processed data matches the data on Carto)
[ x] Does the folder name and python script file name match the dataset_name variable in the script? Are they all lowercase? Does the processing script end in '_processing.py'? (this part is often forgotten)

Mistakenly uploaded Mac DS store file..

chrowe · 2025-02-04T21:57:17Z

@bkrram how would you feel about moving this over to https://github.com/wri/agriadapt-data
I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more.

bkrram · 2025-02-05T08:32:39Z

Sure, I'll do that.

…

On Wed, Feb 5, 2025 at 3:27 AM Chris Rowe ***@***.***> wrote: @bkrram <https://github.com/bkrram> how would you feel about moving this over to https://github.com/wri/agriadapt-data I think it would be good to have all the code you have been working on there, since RW is not really being maintained any more. — Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEC3QHBDY2HVPUVGLA6TLD2OEZVFAVCNFSM6AAAAABWLLH2JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGE3DIMRYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Raghuramand others added 2 commits February 3, 2025 12:04

Script to upload the datasets for cli.081-085
c194374

Delete cli_081_india_andhra_tn_climate_projections/.DS_Store
1a5cc1a
Mistakenly uploaded Mac DS store file..

bkrram requested a review from chrowe February 3, 2025 06:40

chrowe removed their request for review July 21, 2025 16:57

Uh oh!

Conversation

bkrram commented Feb 3, 2025

Checklist for Reviewing a Pre-Processing Script

Uh oh!

chrowe commented Feb 4, 2025

Uh oh!

bkrram commented Feb 5, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

bkrram commented Feb 3, 2025

Checklist for Reviewing a Pre-Processing Script

Uh oh!

chrowe commented Feb 4, 2025

Uh oh!

bkrram commented Feb 5, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

bkrram commented Feb 3, 2025

Checklist for Reviewing a Pre-Processing Script

Uh oh!

chrowe commented Feb 4, 2025

Uh oh!

bkrram commented Feb 5, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

bkrram commented Feb 3, 2025

Checklist for Reviewing a Pre-Processing Script

Uh oh!

chrowe commented Feb 4, 2025

Uh oh!

bkrram commented Feb 5, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

bkrram commented Feb 3, 2025

Checklist for Reviewing a Pre-Processing Script

Uh oh!

chrowe commented Feb 4, 2025

Uh oh!

bkrram commented Feb 5, 2025 via email

Uh oh!

Reviewers

Assignees

Labels