Skip to content
This repository has been archived by the owner on Jul 18, 2024. It is now read-only.

[DataCap Application] <NOAA GFS-HRRR-GEFS> <1/5> #1650

Closed
1 of 2 tasks
caoxinhe0108 opened this issue Feb 22, 2023 · 59 comments
Closed
1 of 2 tasks

[DataCap Application] <NOAA GFS-HRRR-GEFS> <1/5> #1650

caoxinhe0108 opened this issue Feb 22, 2023 · 59 comments

Comments

@caoxinhe0108
Copy link

Data Owner Name

National Oceanic and Atmospheric Administration

Data Owner Country/Region

United States

Data Owner Industry

Environment

Website

https://registry.opendata.aws/noaa-gefs/

Social Media

Website: https://www.noaa.gov/
Twitter: https://twitter.com/NOAA

https://registry.opendata.aws/noaa-gefs/ 
https://registry.opendata.aws/noaa-hrrr-pds 
https://registry.opendata.aws/noaa-gefs

Total amount of DataCap being requested

5PiB

Weekly allocation of DataCap requested

400TiB

On-chain address for first allocation

f1ais6zhflnr5izuabqcibedpvbjcurjzybzcnqpa

Custom multisig

  • Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

NOAA is an agency that enriches life through science. Their reach goes from the surface of the sun to the depths of the ocean floor as we work to keep the public informed of the changing environment around them.

The HRRR is a NOAA real-time 3-km resolution, hourly updated, cloud-resolving, convection-allowing atmospheric model, initialized by 3km grids with 3km radar assimilation. Radar data is assimilated in the HRRR every 15 min over a 1-h period adding further detail to that provided by the hourly data assimilation from the 13km radar-enhanced Rapid Refresh.

The Global Ensemble Forecast System (GEFS), previously known as the GFS Global ENSemble (GENS), is a weather forecast model made up of 21 separate forecasts, or ensemble members. The National Centers for Environmental Prediction (NCEP) started the GEFS to address the nature of uncertainty in weather observations, which is used to initialize weather forecast models. The GEFS attempts to quantify the amount of uncertainty in a forecast by generating an ensemble of multiple forecasts, each minutely different, or perturbed, from the original observations. With global coverage, GEFS is produced four times a day with weather forecasts going out to 16 days.

Is this project associated with other projects/ecosystem stakeholders?

No

If answered yes, what are the other projects/ecosystem stakeholders

No response

Describe the data being stored onto Filecoin

NOAA is an agency that enriches life through science. Their reach goes from the surface of the sun to the depths of the ocean floor as we work to keep the public informed of the changing environment around them.

The HRRR is a NOAA real-time 3-km resolution, hourly updated, cloud-resolving, convection-allowing atmospheric model, initialized by 3km grids with 3km radar assimilation. Radar data is assimilated in the HRRR every 15 min over a 1-h period adding further detail to that provided by the hourly data assimilation from the 13km radar-enhanced Rapid Refresh.

The Global Ensemble Forecast System (GEFS), previously known as the GFS Global ENSemble (GENS), is a weather forecast model made up of 21 separate forecasts, or ensemble members. The National Centers for Environmental Prediction (NCEP) started the GEFS to address the nature of uncertainty in weather observations, which is used to initialize weather forecast models. The GEFS attempts to quantify the amount of uncertainty in a forecast by generating an ensemble of multiple forecasts, each minutely different, or perturbed, from the original observations. With global coverage, GEFS is produced four times a day with weather forecasts going out to 16 days.

Where was the data currently stored in this dataset sourced from

AWS Cloud

If you answered "Other" in the previous question, enter the details here

No response

How do you plan to prepare the dataset

lotus

If you answered "other/custom tool" in the previous question, enter the details here

No response

Please share a sample of the data

350-resule 
2022-06-27 08:00:43   34 Bytes sst.20220626/rtgssthr_grb_0.5.grib2.idx
2022-06-28 08:00:22    2.2 MiB sst.20220627/rtgssthr_grb_0.083.grib2
2022-06-28 08:00:21   34 Bytes sst.20220627/rtgssthr_grb_0.083.grib2.idx
2022-06-28 08:00:21    3.7 MiB sst.20220627/rtgssthr_grb_0.083_awips.grib2
2022-06-28 08:00:21   34 Bytes sst.20220627/rtgssthr_grb_0.083_awips.grib2.idx
2022-06-28 08:00:21  122.8 KiB sst.20220627/rtgssthr_grb_0.5.grib2
2022-06-28 08:00:21   34 Bytes sst.20220627/rtgssthr_grb_0.5.grib2.idx

Total Objects: 64802983
   Total Size: 1.7 PiB
357-resule 
2020-08-25 17:22:47  398.4 MiB hrrr_v2.20160823/conus/hrrr.t09z.wrfprsf13.grib2
2020-08-25 17:22:52  396.0 MiB hrrr_v2.20160823/conus/hrrr.t09z.wrfprsf14.grib2
2020-08-25 17:22:52  394.6 MiB hrrr_v2.20160823/conus/hrrr.t09z.wrfprsf15.grib2
2020-08-25 17:22:52  390.2 MiB hrrr_v2.20160823/conus/hrrr.t09z.wrfprsf16.grib2
2020-08-25 17:23:08  387.1 MiB hrrr_v2.20160823/conus/hrrr.t09z.wrfprsf17.grib2
2020-08-25 17:23:05  384.8 MiB hrrr_v2.20160823/conus/hrrr.t09z.wrfprsf18.grib2
2021-09-28 03:48:22   31.6 KiB index.html

Total Objects: 43282174
   Total Size: 2.1 PiB
347-resule 
2023-02-15 13:35:33   13.5 MiB gefs.20230215/00/wave/gridded/gefs.wave.t00z.p30.global.0p25.f258.grib2
2023-02-15 13:35:31    1.2 KiB gefs.20230215/00/wave/gridded/gefs.wave.t00z.p30.global.0p25.f258.grib2.idx
2023-02-15 13:38:42   13.5 MiB gefs.20230215/00/wave/gridded/gefs.wave.t00z.p30.global.0p25.f264.grib2
2023-02-15 13:37:38    1.2 KiB gefs.20230215/00/wave/gridded/gefs.wave.t00z.p30.global.0p25.f264.grib2.idx
2023-02-15 13:40:59   13.5 MiB gefs.20230215/00/wave/gridded/gefs.wave.t00z.p30.global.0p25.f270.grib2
2023-02-15 13:40:57    1.2 KiB gefs.20230215/00/wave/gridded/gefs.wave.t00z.p30.global.0p25.f270.grib2.idx
2021-09-28 03:47:57   31.6 KiB index.html

Total Objects: 116639180
   Total Size: 2.2 PiB

Confirm that this is a public dataset that can be retrieved by anyone on the Network

  • I confirm

If you chose not to confirm, what was the reason

No response

What is the expected retrieval frequency for this data

Monthly

For how long do you plan to keep this dataset stored on Filecoin

1.5 to 2 years

In which geographies do you plan on making storage deals

Greater China, Asia other than Greater China, North America

How will you be distributing your data to storage providers

Cloud storage (i.e. S3)

How do you plan to choose storage providers

Slack, Big data exchange

If you answered "Others" in the previous question, what is the tool or platform you plan to use

No response

If you already have a list of storage providers to work with, fill out their names and provider IDs below

No response

How do you plan to make deals to your storage providers

Boost client, Lotus client

If you answered "Others/custom tool" in the previous question, enter the details here

No response

Can you confirm that you will follow the Fil+ guideline

Yes

@large-datacap-requests
Copy link

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

@large-datacap-requests
Copy link

Thanks for your request!
Everything looks good. 👌

A Governance Team member will review the information provided and contact you back pretty soon.

@herrehesse
Copy link

Dear Filecoin+ Github applicant,

We have noticed that the dataset is already (partly) on chain. While we appreciate your enthusiasm to contribute to the Filecoin network, we want to remind you that this behaviour may not be beneficial to the network. Can you explain to me what happend here?

Thank you for your understanding and cooperation.

Screenshot 2023-02-22 at 13 00 32

@caoxinhe0108 caoxinhe0108 changed the title [DataCap Application] <NOAA GFS-HRRR-GEFS> --01 [DataCap Application] <NOAA GFS-HRRR-GEFS> <1/5> Feb 22, 2023
@large-datacap-requests
Copy link

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

@large-datacap-requests
Copy link

Thanks for your request!
Everything looks good. 👌

A Governance Team member will review the information provided and contact you back pretty soon.

@caoxinhe0108
Copy link
Author

Thank you for paying attention to my application, we are also very interested in this data. I have observed that only 1483 has been partially stored, and the rest has not yet begun. We also hope that it can be stored.
Let's contribute to the NOAA project storage together

@Sunnyiscoming Sunnyiscoming self-assigned this Feb 28, 2023
@Sunnyiscoming
Copy link
Collaborator

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

400TiB

Client address

f1ais6zhflnr5izuabqcibedpvbjcurjzybzcnqpa

@large-datacap-requests
Copy link

large-datacap-requests bot commented Feb 28, 2023

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1ais6zhflnr5izuabqcibedpvbjcurjzybzcnqpa

DataCap allocation requested

200TiB

Id

8f98e032-c835-459b-9542-059c3d27df61

@kernelogic
Copy link

kernelogic commented Feb 28, 2023

@caoxinhe0108 is not a new account. This public dataset is not overly crowded. Willing to support. Could you also provide some distribution plan? I.e. miner IDs and regions?

Copy link

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacead453fhectz6qp6ug7xlyax65da77gwmwnixmzcgnxyjns3hid26

Address

f1ais6zhflnr5izuabqcibedpvbjcurjzybzcnqpa

Datacap Allocated

200.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

Id

8f98e032-c835-459b-9542-059c3d27df61

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacead453fhectz6qp6ug7xlyax65da77gwmwnixmzcgnxyjns3hid26

@caoxinhe0108
Copy link
Author

Thank you Notary, we have contacted 6 SPs
f02006841
f01914268
f01896036
f02024315
f02013434
f02044834
They are located in Southeast Asia, North America, Greater China and other regions;
thanks again for signing it;

@large-datacap-requests
Copy link

DataCap Allocation requested

Request number 6

Multisig Notary address

f02049625

Client address

f1ais6zhflnr5izuabqcibedpvbjcurjzybzcnqpa

DataCap allocation requested

2.87TiB

Id

71c65baa-879b-4e97-a757-ab04b7235fcf

@large-datacap-requests
Copy link

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1ais6zhflnr5izuabqcibedpvbjcurjzybzcnqpa

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

2.87TiB

Total DataCap granted for client so far

1.927837729454041e+52YiB

Datacap to be granted to reach the total amount requested by the client (5PiB)

-2.33B

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
68918 18 2.07PiB 8.29 525.24TiB

@filplus-checker-app
Copy link

DataCap and CID Checker Report Summary1

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients2

✔️ No CID sharing has been observed.

Full report

Click here to view the full report.

Footnotes

  1. To manually trigger this report, add a comment with text checker:manualTrigger

  2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests