Skip to content
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

WISPR data Fido search from VSO - update resulted results table #7248

Open
hayesla opened this issue Oct 19, 2023 · 3 comments
Open

WISPR data Fido search from VSO - update resulted results table #7248

hayesla opened this issue Oct 19, 2023 · 3 comments
Labels
Feature Request New feature wanted! net Affects the net submodule Remote Server Issue / VSO An issue that is caused by unexpected or incorrect behaviour on a VSO server.

Comments

@hayesla
Copy link
Member

hayesla commented Oct 19, 2023

Describe the feature

Now you can query the VSO for WISPR data, and pass attributes of a.Detector and a.Level.

For example:

res = Fido.search(a.Time("2022-09-06", "2022-09-07"), a.Instrument.wispr, a.Detector("inner"), a.Level(3))
res
<sunpy.net.fido_factory.UnifiedResponse object at 0x122e2ec10>
Results from 1 Provider:

164 Results from the VSOClient:
Source: http://vso.stanford.edu/cgi-bin/search
Total estimated size: 648.568 Mbyte

       Start Time               End Time        Source Instrument    Wavelength    Provider  Physobs  Wavetype  Extent X   Extent Y  Extent Width Extent Length Extent Type   Size 
                                                                      Angstrom                                                                                               Mibyte
----------------------- ----------------------- ------ ---------- ---------------- -------- --------- -------- ---------- ---------- ------------ ------------- ----------- -------
2022-09-06 00:00:21.000 2022-09-06 00:01:01.000    PSP      WISPR 4900.0 .. 7400.0      NRL intensity  visible 32.0667715 -6.7786505   40.6128000    43.3203200 FAR_OFF_SUN 3.77148
2022-09-06 00:07:46.000 2022-09-06 00:08:27.000    PSP      WISPR 4900.0 .. 7400.0      NRL intensity  visible 32.0689175 -6.7673351   40.6128000    43.3203200 FAR_OFF_SUN 3.77148
2022-09-06 00:15:13.000 2022-09-06 00:15:54.000    PSP      WISPR 4900.0 .. 7400.0      NRL intensity  visible 32.0711924 -6.7555905   40.6128000    43.3203200 FAR_OFF_SUN 3.77148
2022-09-06 00:22:38.000 2022-09-06 00:23:19.000    PSP      WISPR 4900.0 .. 7400.0      NRL intensity  visible 32.0734360 -6.7439820   40.6128000    43.3203200 FAR_OFF_SUN 3.77148
2022-09-06 00:30:14.000 2022-09-06 00:30:55.000    PSP      WISPR 4900.0 .. 7400.0      NRL intensity  visible 32.0757230 -6.7319755   40.6128000    43.3203200 FAR_OFF_SUN 3.77148

however these attributes do not show up in teh returned table, so a user may not necessarily know you can do this

Proposed solution

No response

@hayesla hayesla added the Feature Request New feature wanted! label Oct 19, 2023
@Cadair
Copy link
Member

Cadair commented Oct 19, 2023

Can you include the output of the search (bonus points for a search with a single result) with debug logging on?

@hayesla
Copy link
Member Author

hayesla commented Oct 20, 2023

In [12]: res = Fido.search(a.Time("2022-09-06", "2022-09-06 00:01:02"), a.Instrument.wispr, a.Detector("inner"), a.Level(3))
DEBUG: VSO Request:
 <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:VSO="http://virtualsolar.org/VSO/VSOi">
  <soap-env:Body>
    <VSO:Query>
      <body>
        <block>
          <time>
            <start>20220906000000</start>
            <end>20220906000102</end>
          </time>
          <instrument>WISPR</instrument>
          <level>3</level>
          <detector>inner</detector>
        </block>
      </body>
    </VSO:Query>
  </soap-env:Body>
</soap-env:Envelope>
 [sunpy.net.vso.zeep_plugins]
DEBUG: VSO Response:
 <soap:Envelope xmlns:VSO="http://virtualsolar.org/VSO/VSOi" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <soap:Body>
    <VSO:QueryResponse>
      <body>
        <provideritem>
          <no_of_records_returned>1</no_of_records_returned>
          <no_of_records_found>1</no_of_records_found>
          <record>
            <recorditem>
              <info>L3</info>
              <fileid>data/psp/wispr/L3/orbit13/inner/20220906/psp_L3_wispr_20220906T000016_V1_1211.fits</fileid>
              <source>PSP</source>
              <wave>
                <wavemin>4900</wavemin>
                <wavetype>visible</wavetype>
                <wavemax>7400</wavemax>
                <waveunit>Angstrom</waveunit>
              </wave>
              <time>
                <start>20220906000021</start>
                <end>20220906000101</end>
              </time>
              <provider>NRL</provider>
              <instrument>WISPR</instrument>
              <extent>
                <width>40.6128000</width>
                <x>32.0667715</x>
                <length>43.3203200</length>
                <type>FAR_OFF_SUN</type>
                <y>-6.7786505</y>
              </extent>
              <size>3862</size>
              <physobs>intensity</physobs>
            </recorditem>
          </record>
          <provider>NRL</provider>
          <version>1</version>
        </provideritem>
      </body>
    </VSO:QueryResponse>
  </soap:Body>
</soap:Envelope>
 [sunpy.net.vso.zeep_plugins]

@Cadair
Copy link
Member

Cadair commented Oct 20, 2023

@sunpy/vso-contacts I think these things should come back down in the QueryResponse?

@nabobalis nabobalis added net Affects the net submodule Remote Server Issue / VSO An issue that is caused by unexpected or incorrect behaviour on a VSO server. labels Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature wanted! net Affects the net submodule Remote Server Issue / VSO An issue that is caused by unexpected or incorrect behaviour on a VSO server.
Projects
None yet
Development

No branches or pull requests

3 participants