Skip to content
New issue

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

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

Already on GitHub? # to your account

[View > Files > External Data] nothing shows up #28

Closed
Xarthisius opened this issue Apr 14, 2020 · 2 comments · Fixed by #78
Closed

[View > Files > External Data] nothing shows up #28

Xarthisius opened this issue Apr 14, 2020 · 2 comments · Fixed by #78
Labels
bug Something isn't working question Further information is requested

Comments

@Xarthisius
Copy link
Contributor

Steps to Reproduce

  1. Deploy and register LIGO Tale
  2. Tale Dashboard > Public Tales: click "View" on "LIGO Tutorial"
  3. Navigate to Files > External Data

Expected Results
See the content of the Tale's dataSet.

Actual Results
Panel is empty.

@Xarthisius Xarthisius added the bug Something isn't working label Apr 14, 2020
@bodom0015
Copy link
Member

bodom0015 commented May 28, 2020

There appears to be some error in registering the LIGO HTTPS resources. Performing a GET against the /dataset endpoint does not yield any of the expected LIGO datasets that should have been registered by python ./register_ligo.py, but instead has this seemingly invalid entry in their place:

  {
    "_id": "5ecf0070d0abc71e296340a0",
    "_modelType": "folder",
    "created": "2020-05-28T00:06:08.145000+00:00",
    "creatorId": "5ec313fc88049a867e342730",
    "description": "",
    "identifier": "https://www.gw-openscience.org",
    "name": "www.gw-openscience.org",
    "provider": "HTTPS",
    "size": 0,
    "updated": "2020-05-28T00:06:12.469000+00:00"
  }

Could this possibly be the same issue as whole-tale/girder_wholetale#304?

@bodom0015 bodom0015 added the question Further information is requested label May 28, 2020
@Xarthisius
Copy link
Contributor Author

I don't think /dataset is relevant here. Data Catalog in Whole Tale is a nested structure and objects in Tale's dataSet can be added from within the Catalog hierarchy. Therefore they may not appear in neither /dataset?myData=False, nor /dataset?myData=True and LIGO is actually a good example of that. I'll comment on whole-tale/girder_wholetale#304 why it's an expected behavior.

After a successful deployment, you can verify the validity of the LIGO Tale (and its dataset) in a three ways:

  1. Run the tale and using a terminal in jupyter call ls ../data
  2. Using Girder's swagger run GET /tale/{id} and see if dataSet is populated. It should look roughly like this:
    {
       "_accessLevel": 0,
       "_id": "5ecf8956192e6e339a473873",
       "_modelType": "tale",
       "authors": [
          {
            "firstName": "Kacper",
            "lastName": "Kowalik",
            "orcid": "https://orcid.org/0000-0003-1709-3744"
          }
        ],
       ...
       "dataSet": [
          {
            "_modelType": "item",
            "itemId": "5ecf8950192e6e339a473855",
            "mountPath": "BBH_events_v3.json"
          },
          {
            "_modelType": "item",
            "itemId": "5ecf8950192e6e339a473858",
            "mountPath": "GW150914_4_template.hdf5"
          }
          ...
    
  3. Go to [View > Files > External Data] using old dashboard.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants