[DataCap Application] JMA Himawari-8/9

Flora-Moody commented 1 year ago

Data Owner Name

NOAA

Data Owner Country/Region

Japan

Data Owner Industry

Environment

Website

https://www.noaa.gov/

Social Media

https://www.facebook.com/NOAA
https://www.youtube.com/usnoaagov

Total amount of DataCap being requested

5PiB

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f1u3gc4fsh47pvrszv3otngb2t5hm3ycmtx7jxxny

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

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. Our 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.

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

Himawari-8, stationed at 140E, owned and operated by the Japan Meteorological Agency (JMA), is a geostationary meteorological satellite, with Himawari-9 as on-orbit back-up, that provides constant and uniform coverage of east Asia, and the west and central Pacific regions from around 35,800 km above the equator with an orbit corresponding to the period of the earth’s rotation.

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

IPFS, lotus, singularity

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

No response

Please share a sample of the data

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

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

[X] I confirm

If you chose not to confirm, what was the reason

No response

What is the expected retrieval frequency for this data

Yearly

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, Europe

How will you be distributing your data to storage providers

Cloud storage (i.e. S3), HTTP or FTP server, Shipping hard drives

How do you plan to choose storage providers

Slack, Filmine, 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

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 0.00%
Overall HTTP retrieval success rate: 4.73%
Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 50.28% of deals are for data replicated across less than 4 storage providers.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

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

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

spaceT9 commented 1 year ago

A little advice: you need to contact your sps to increase retrieval rate before next tranche

Flora-Moody commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 0.00%
Overall HTTP retrieval success rate: 7.93%
Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 52.39% of deals are for data replicated across less than 4 storage providers.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

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

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

Flora-Moody commented 1 year ago

@Filplus-govteam Done for the form.

Wengeding commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 0.00%
Overall HTTP retrieval success rate: 8.11%
Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 52.00% of deals are for data replicated across less than 4 storage providers.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

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

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

Wengeding commented 1 year ago

Looks good to me about your retrieval dashboard.

Wengeding commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedqayxt4nxxtmtfyrpjgd6lfibxcepxlm6x7rty45mv7zgac4jm4a

Address

f1u3gc4fsh47pvrszv3otngb2t5hm3ycmtx7jxxny

Datacap Allocated

2.00PiB

Signer Address

f1txfsjmix4vlzido4dkildrnbw26owtlbslexmpa

Id

b2fc6540-0613-474e-b83e-55a03bf8e353

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

AthSmith commented 1 year ago

Great to see that retrieval success rate is on the rise, keep up!

AthSmith commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebxlqamsr2bdhxgtyx4tslbo7tucr6anuvqi3tejg2adyq2reyhyk

Address

f1u3gc4fsh47pvrszv3otngb2t5hm3ycmtx7jxxny

Datacap Allocated

2.00PiB

Signer Address

f1vxbqrf7rfum3n6m5u6eb4re6xj7amvsaqnzu64y

Id

b2fc6540-0613-474e-b83e-55a03bf8e353

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

ghost commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 0.00%
Overall HTTP retrieval success rate: 8.81%
Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 51.99% of deals are for data replicated across less than 4 storage providers.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

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

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

ghost commented 1 year ago

SPs provided

f0397855 | Andy | HK | f0518877 | LisaWu | CN | f01203032 | Mandy | CN | f01202610 | Calvin | HK | f0128166 | Robert | KR |

Actual SPs used: https://github.com/data-preservation-programs/filplus-checker-assets/blob/main/filecoin-project/filecoin-plus-large-datasets/issues/1860/1692210362327.md

Does not match here @Flora-Moody can you explain?

Also full disregard of signing process for #922 by @Wengeding @AthSmith - grounds for removal. FYI @raghavrmadya

ghost commented 1 year ago

other flags: limited retrievals no distribution (less than 4 SPs storing) no geo distribution

AthSmith commented 1 year ago

Hey@Filplus-govteam ,thanks for your kind input.

1、The retrieval success rate is clearly shown in the report and I don't see anything inappropriate. Also all bandwidths are limited and retrieval relies heavily on bandwidth resource and entire link.

2、There are 27(not less than 4) SPs distributed by this applicaiton as the report, i think it's ok;

3、Up to now there is no evidence that these 27 SPs are located in the same IDC. if there is, I agree with the removal.

Also, I reserve my opinion on whether SP can be flexible in its distribution. Thanks a lot!

cryptowhizzard commented 1 year ago

Before you start here @AthSmith

I did a Hexdump on the data i could retrieve from you with deal ID 49193893 : hexdump -C 1860-f02100529-f02245242-49193893-baga6ea4seaqpiup55s2xofck5xibnkr7hpvbzyiinucmgbs3lyoynlydursfsmy |more

Seems that you are not storing real data.

I invite you to upload baga6ea4seaqpiup55s2xofck5xibnkr7hpvbzyiinucmgbs3lyoynlydursfsmy here on this link so we can review and inspect the whole carfile.

Thanks!

AthSmith commented 1 year ago

I didn't see any logic in your conclusions and suggest you stop gaslighting if you don't have more evidence.

Also, if you don't believe the official report, suggest you share your methodology with Xinan. I do think your comment has no credibility as you're in a profitable DC business.

cryptowhizzard commented 1 year ago

The data stored is not the data the applicant told us he was going to store, proof is above. It’s pure fraud and your name tag is on it for eternity making your reputation worthless.

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.

-- Commented by Stale Bot.

large-datacap-requests[bot] commented 1 year ago

The issue reached the total datacap requested. This should be closed

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1u3gc4fsh47pvrszv3otngb2t5hm3ycmtx7jxxny

Rule to calculate the allocation request amount

total dc reached

DataCap allocation requested

0

Total DataCap granted for client so far

1.8626451492309573e+53YiB

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

1.8626451492309573e+53YiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
126378	29	2PiB	13.58	871.37TiB

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.

-- Commented by Stale Bot.

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!

-- Commented by Stale Bot.

filecoin-project / filecoin-plus-large-datasets