DKIST Data Center Archive Search Manual

DKIST Data Center Archive Search Manual

 

What’s New?

What’s New?

  • Jan 6, 2026

    • Deleted the prior update from Oct 14. Updated the manual to show that the filter to search by Polarimetric Sensitivity (was Accuracy) is not currently available, as explained in the text.

  • Oct 14, 2025

    • Updated Section 2.6.8 Polarimetric Accuracy → Polarimetric Sensitivity.

  • Aug 28, 2025

    • Updated manual for some unit corrections in the portal.

    • Added section about what to do if you forget to start a personal endpoint while trying to download data.

    • Added informational notes about the Fried Parameter.

    • Added informational notes about how the rounding the portal does on display, may make it appear that results outside of the filter bounds are being presented.

  • Jul 14, 2025

    • Updating the manual for the new Product ID.

      • For each dataset created by an Experiment, a unique ID, known as the Product ID (e.g., L1-JAZXI) is created. The Product ID is a new identifier created to address the problem that Dataset IDs are not preserved through reprocessing. The Product ID will stay the same no matter how many times a dataset is reprocessed. This makes it the ideal ID for sharing datasets with other users. See also https://nso.atlassian.net/wiki/spaces/DDCHD/pages/3692036131.

Table of Contents

Table of Contents

1. Introduction

The DKIST Data Center Search Portal is one of the main tools which can be used to access DKIST data. It presents a clear, visual interface to the calibrated DKIST datasets. The portal enables search, filter and download functionality for all public datasets, and while the portal allows the metadata of all datasets to be searched, a user will only be allowed to download datasets for which they are a PI or Co-I during the exclusive access period. The portal makes use of search filters which present a rich interface to find datasets of interest, with granularity that stretches from individual datasets through all the datasets generated in an experiment for a proposal. In addition, searching using filters such as wavelength or spectral line, spatial coordinates or whether an observation contains polarization data, allows for broad searches across the entire archive. These filters are key to the operation of the portal, and are described in great detail below. Lastly, along with the ability to create new search filters, another key feature of the portal is being able to save the filters so that they can be reused e.g., to find previously searched for datasets.

1.1 DKIST Data Products

Datasets from the DKIST instruments are both large and complex. In order to maximize the scientific return from the data, it is necessary to provide calibrated data products to the user. The Data Center is responsible for calibrating the raw data received from the telescope into Level 1 data products. As the raw data is received, it is divided into processing candidates that will be used to created one processed dataset. A dataset is roughly defined by the following items:

  • Instrument

  • Broad wavelength

  • Similar instrument parameters

For example, an experiment that uses VBI with observations in Ca II K (393.327 nm) and H-beta (486.139 nm), and DL-NIRSP with observations in Fe XI (789 nm) and Ca II (854.2 nm), would result in 4 datasets. 

Each dataset contains a series of calibrated Level 4 compliant FITS files with image data and attached headers, and is provided as one calibrated frame per FITS file. In addition to the calibrated data files, a dataset also contains a quality report, a browse movie and one ASDF file to support the DKIST User Tools and enable more granular data discovery. All of these files, are available along with the datasets via the search portal and also the User Tools.

1.1.1 Level 1 Data

The calibrated (Level 1) datasets consist primarily of sets of FITS files that are part of the same instrument program. The aim of the calibration is to remove as many of the telescope and instrumental effects as possible. Initial calibration codes are based upon those supplied by the Instrument teams. Undoubtedly, upgrades to the calibration routines or additional routines will be needed as experience is gained in working with each instrument. Data users are encouraged to provide feedback to the Data Center on additional calibration steps they might find necessary to perform their science. Please see also https://nso.atlassian.net/wiki/spaces/DDCHD/pages/1803158003

1.1.2 ASDF File

The Advanced Scientific Data Format (ASDF) is a next-generation interchange format for scientific data. Although it can be used to store image data as well, the Data Center is using it to store all of the header information as well as world coordinate information and file ordering for all of the FITS files contained in a dataset. The User Tools makes use of this information to present a unified view of the dataset, enable finer grained filtering on any header field (not possible with the Search Portal), and selective downloading of files.

1.1.3 Browse Movie

In order to give a user a snapshot of the data contained in a dataset, a browse movie is created for each dataset.

1.1.4 Quality Report

It is vitally important for both the Data Center and scientists to be confident in the files created through the calibration process. To this end, with each processed dataset, a Quality Report is created. This report details the steps that were used to create the calibrated dataset and any errors that were encountered in the process. This could be, for example, a smaller than optimal number of dark frames to use in averaging for the dark calibration step. In addition, the Quality Report will also contain information about the weather conditions, sky brightness and seeing, which may assist a scientist to find datasets or parts of datasets of interest more easily.

1.1.5 Level 2 Data Products

Separate from the Data Center calibration effort, there is an effort to create higher order data products, such as magnetograms, from the publicly available data. It is envisioned that this effort would regularly create higher order products for a small number of lines. In the future these higher order products will also be available from the portal.

1.2 Downloading DKIST Data

When dealing with datasets that DKIST will create (on the order of multiple Terabytes), old methods of data transfer like FTP are just not suitable. In addition, given that the Data Center only has access to finite networking resources, the Data Center needs to be able to shape and limit requests in such a way as to ensure a fair distribution of the resources to all data requestors.

Delivering DKIST data to the scientist thus requires a system that:

  • will be stateful

  • can continue if interrupted without restarting

  • can deal with transfers that might last many days and

  • guarantees the veracity of the downloaded data 

In order to provide scientists with the best possible download experience, DKIST DC is using Globus to transfer files to users. (See https://www.globus.org/data-transfer .)

Downloading DKIST data will necessitate a few extra steps, including creating a Globus account and having to define an "endpoint" for a user’s data.

An "endpoint" is one of the two file transfer locations – either the source or the destination – between which files can move. Once a resource (server, cluster, storage system, laptop, or other system) is defined as an endpoint, it will be available to authorized users who can transfer files to or from this endpoint. Authorized Users are users (PI, Co-Is) that are part of the proposal team, for which data was taken. Only authorized users can download the data during the exclusive access period.

The DKIST Data Center will be the source endpoint, and the destination endpoint will be a place at a user's institution or research group facility designed for downloading large datasets. It will also be possible to download datasets/subsets to a user’s laptop, but these datasets will be very large. (See also Logging in to Globus below.)

Users will be able to search for datasets without being logged in, but users will need to authenticate with Globus in order to download datasets. Note that searches may display datasets that are currently in the exclusive access period. Although metadata is available with respect to these searches, a user will not be able to download the data unless they are part of the proposal team until the exclusive access period has expired.

2. Searching for DKIST Data

The primary search mechanism for DKIST data is the search portal. Figure 1. below displays the default view when a user accesses the search portal dashboard. By default, the portal will display datasets sorted by the Dataset Creation Date, newest first. Note that while datasets may show up in the search, some may only be downloadable by the PIs or Co-Is of the particular proposal to which the dataset belongs during the exclusive access period.

Screen Shot 2025-07-28 at 11.02.16 AM.png
Figure 1. Default portal view.

The search portal uses search filters to construct queries that return datasets that match the many search filter criteria options. These search filters are shown on the left panel of the portal. One such filter example is given below, for data taken between 2025/06/17 20:00 and 2025/06/17 22:00 UTC. An in depth look at the portal filters is given below.

2.1 Search Results 

Screen Shot 2025-07-28 at 11.07.37 AM.png
Figure 2. Basic experiment execution date range search with the portal.

The standard search results are summarized below. As filters are applied, the number of matching datasets is continuously updated. The portal also lets a user know how many datasets in total have been processed and how many are currently selected for download.

Screen Shot 2025-05-08 at 12.45.48 PM.png
Figure 3. Summary of results matching the current filter including those selected for download.

Below the summary the user will find the results table. The fields are described below in table 1.

Screen Shot 2025-07-28 at 2.50.48 PM.png
Figure 4. Results from the filtered data search. Two of the datasets have been added to the search cart.
Screen Shot 2025-07-28 at 2.53.44 PM.png
Figure 5. Click on the up/down arrows to the right of the proposal description summary to view the full proposal description text. As indicated by the red symbol on the far left of the results summary, this dataset is still within the exclusive access period.

Field

Description

Field

Description

Screen Shot 2025-05-08 at 1.13.18 PM.png

Add the dataset to the cart for download via Globus.

Screen Shot 2025-05-08 at 1.13.45 PM.png

Add all the datasets to the cart for download via Globus.

Screen Shot 2025-05-08 at 1.13.25 PM.png

Remove the dataset from the cart.

Screen Shot 2025-05-08 at 1.17.23 PM.png

Remove all the datasets from the cart.

Screen Shot 2025-07-22 at 7.52.39 AM.png

The dataset is in exclusive access period and is generally not downloadable. Login if you are the PI/Co-I to download the data. See Section 2.3 for more details on exclusive access periods.

Screen Shot 2025-05-08 at 1.20.48 PM.png

Download the ASDF file for this dataset.

Screen Shot 2025-05-08 at 1.20.58 PM.png

Download the Quality Report for this Dataset.

Screen Shot 2025-05-08 at 1.21.17 PM.png

View the browse movie for this dataset.

Proposal ID

This dataset is within the exclusive access period. Click the symbol for more information. If you are the principal investigator for this dataset, you will need to login to download it.

Product ID

The unique ID for each dataset which is part of the proposal. See also more on the Product ID.

Description

The unique ID of the dataset. Click on the link for more information about the observations in the dataset. See figures 6-8.

Observation Wavelength

The wavelengths contained within the dataset.

Dataset Creation Date

The date at which the dataset was created after calibration by the Data Center.

Experiment Execution Date

The date that the experiment was executed on. Experiments are what creates the observations for a dataset as part of a proposal.

Instrument

The instrument that took the dataset

Table 1. Key to the icons and fields on the results page

Clicking on the Product ID will give the user more information on that particular dataset. This is illustrated below.

Screen Shot 2025-08-28 at 4.39.09 PM.png
Figure 6a. Example of part of the details page for each dataset.

The top half of the dataset details pages contains links to download the Movie Preview file, the ASDF file and the Quality Report. If you are not logged in and the dataset is within the exclusive access period, then you will see the red banner indicating the dataset is not available for download. If you are logged in as the PI or the dataset is publicly available then there will not be an exclusive access period banner, and instead there will be a link to add the dataset to the cart as show below.

Screen Shot 2025-07-28 at 9.13.47 PM.png
Figure 6b. Button to add dataset to to cart

Additionally you will be able to play the preview movie in browser. The full description of the proposal is given, and in addition a link to the code that was used to calibrate the data is provided.

Screen Shot 2025-08-28 at 4.39.30 PM.png
Figure 6c. Example of part of the details page for each dataset

Additional information about the dataset is also presented on the details page. The pages also lists other datasets that were part of the observing program that created the dataset and all datasets available under the particular proposal. Users are also urged to consider looking at the quality report for more information about the conditions during the observation and any issues that may have arisen during calibration.

Screen Shot 2025-07-28 at 9.20.54 PM.png
Figure 6d. Example of a dataset that have not been reprocessed

The Product ID, is a new ID created to combat the problem that Dataset IDs are not conserved through reprocessing. The Product ID will stay the same no matter how many times a dataset is reprocessed. This makes it the ideal ID for sharing datasets with other users. A new section have been added to the dataset details section (reflected also on the details page for the Product ID) which details the reprocessing of a particular dataset.

Screen Shot 2025-07-21 at 11.26.12 PM.png
Figure 6e. Example of a dataset that have been reprocessed

The figure above contains an example of a dataset that has been reprocessed. Here HQFLOY is the new Dataset ID and BKDJD is the previous Dataset ID. The Data Center keeps available the current and previous datasets, and also notes the one before the previous dataset which will have been deleted. Note here that you can use the Dataset ID to search for data too and it will give you almost identical details pages. From figure 6d, searching for L1-SRPYN (Product ID) and YTSWFH (Dataset ID) access the same information.

2.2 DKIST Dataset Known Issues (Caveats)

Screen Shot 2025-05-08 at 2.05.40 PM.png
Screen Shot 2025-05-08 at 2.04.33 PM.png
Figure 7. The dataset caveats pages.

As the Data Center has worked through the calibration of the ViSP and VBI data, we have worked with NSO scientists and instrument teams to capture the issues we are aware of with the processed datasets. These issues have been captured in the DKIST Data Center Archive Help Desk, in the https://nso.atlassian.net/wiki/spaces/DDCHD/pages/1959985377 page. This page will be continually updated to maintain the latest information about the datasets as they are processed. Caveats for Cryo-NIRSP and DL-NIRSP will be available soon.

2.3 Dataset Exclusive Access Periods

DKIST is implementing an exclusive access period for it scheduled observations. PIs will be given a total of 6 months from when the data is made available by the DC, to analyze their data before it is made public. In the case of datasets being primarily for the thesis work of a PhD student, this term is extended to 12 months. A PI may elect to waive the exclusive access period if they wish too. Although the data itself is subject to an exclusive access period, the metadata is not. As shown above (Figure 4), results may contain data which is not yet public. For more information see https://nso.edu/telescopes/dkist-data-access-policy/

Figure 8. Information about the exclusive access period

 

Clicking on the exclusive access icon (see Table 1) will let a user know how much longer the data will be within that period before becoming public.

2.4 Filtering Search Results

Figure 9: Default appearance of the portal showing filter options

The primary mechanism for data selection is by construction of filters. By using the filters, a user may search on any number of parameters. Filters are additive. A dataset must match all filter criteria (including negated criteria) in order to be displayed. By default, the search portal will display the latest available data with no filtering applied. Figure 9, illustrates the default appearance of the portal showing the filter options.

These options are broken down into Basic and Advanced search filters, as well as provide the functionality to load previously saved filter combinations. The use and display of the filters are described in detail in the following sections.

Note that there are currently few sanity checks on the possible filter values or combinations of filters. It may be entirely possible for the user to specify a filter combination for which there are no valid datasets.

Fields that accept multiple values have their parameters OR'd together while values across parameters are AND'd. These are listed explicitly in the table below.

Search Parameters AND'd

Search Parameters OR'd

Date Range, ­­Spatial, Polarization Observations, Wavelength, Exposure, Fried Parameter, Polarimetric Accuracy, Has Spectral Axis, Spectral Sampling, Temporal Sampling, Spatial Sampling

Instruments, Spectral Line, Proposal ID, Experiment ID, Dataset ID, Product ID, Target Type

Parameters that are OR'd such as Dataset ID may be added more than once to the filter to select multiple datasets.

2.4.1 The Filter Bar

Screen Shot 2025-08-28 at 4.42.16 PM.png
Figure 12: Default filter bar

 

The filter bar displays the current filters that are being used. If nothing is selected, it will appear as illustrated on the left. Within the filter bar there are four filter related options, listed below:

Save Filter. Choose a unique name (max 50 characters) for this filter. This will save the current filter as the name provided.

Load Filter. Select a previously saved filter to load. The drop-down box will list all the filters you have previously saved. (See also Previous Filters)

Share Filter. Will create a URL that you san share with other scientists. This URL will expand to the current filter selection. See Share Current Filter

Clear Filter. This option deletes the current set of filters and reverts back to the default search. (Display latest datasets)

Table 2. The Save, Load, Share and Clear filter options.

Screen Shot 2025-08-28 at 4.44.11 PM.png

 

The filter bar contains a shortcut to enable users to find publicly available datasets.

Table 3. The Display Only Public Datasets short cut.

When a user adds a filter option, it appears to the right of the Current Filter. In the filter bar example below, the portal will search the latest datasets for those that were taken with the VBI instrument. As this filter was loaded from a previously saved filter, the name of the filter is also displayed.

Figure 10. Filter bar with date selection

2.4.2 Negating Filters

For certain filters, such as Has a Spectral Axis, adding that filter without a value sets it to false. The search will look for datasets which do not have a spectral axis, in this case returning only VBI or Cryo-NIRSP context imager data.

Screen Shot 2025-07-28 at 9.46.18 PM.png
Figure 11. Negating a filter option.

2.5 Basic Search Filters

The “Basic” search filters are envisioned to be the primary filters to be used for searching DKIST data. They are Publicly Available Data, Proposal ID, Experiment Start Date Range, Dataset Creation Data Range, Instruments, Spectral Line, Spatial and Polarization Observations. These filters are now described in detail.

2.5.1 Publicly Available Data

This filter enables a user to specify if they want to toggle their search for all data publicly available datasets or for data that is currently within the exclusive access period.

Figure 12. Select a type of dataset access to filter by

Using the dataset access filter, a user can toggle between publicly available data or data that is still within the exclusive access period. The default (no filter) will search both kinds of datasets. Clicking on ADD ACCESS FILTER adds Dataset Access to a user’s current list of selected filters. Note that you can also select the shortcut on the Filter Bar to enable users to find publicly available datasets.

2.5.2 Proposal ID

Figure 13. Select data by proposal ID(s)

 

This filter allows the selection of datasets containing a particular Proposal ID. All observations scheduled with DKIST have a Proposal with a unique ID associated with them. Entering a Proposal ID here, e.g., pid_1_50, and all datasets associated with that ID are displayed. To select multiple Proposal IDs, separate them with commas. Attempting to add a new Proposal ID filter when you already have one selected, will just replace the Proposal ID selection with the new one. Note that while all metadata is available for searching, a user will only be able to download data for which they are the PI or a Co-I during the exclusive access period. Clicking ADD PROPOSAL ID FILTER adds Proposal ID to the current list of selected filters. A user may add more than one Proposal ID to search for by adding a new search ID and clicking on ADD PROPOSAL ID FILTER again.

2.5.3 Experiment Execution Date Range

This filter limits the results to datasets that intersect the specified Experiment Execution Date Range. This is the date at which the experiment was run at the telescope. DKIST data is available from the earliest calibrated observation up until the latest calibrated observation which may lag the current date considerably, so there can be a considerable difference between experiment execution time and dataset creation date (see below). Be aware that too wide an execution date range may end up running into the selection limit of 1000 datasets.

Screen Shot 2025-08-28 at 6.39.22 PM.png
Figure 14. Selecting an experiment execution date range to filter on

2.5.4 Dataset Creation Date Range

This filter limits the results to datasets that intersect the specified Date Range. DKIST data is available from the earliest calibrated observation up until the latest calibrated observation, which may lag the current date considerably. Users should be aware that too wide a date range may end up running into the selection limit of 1000 datasets.

Screen Shot 2024-04-09 at 2.57.03 PM.png
Figure 15. Selecting a dataset creation date range to filter by

Unlike the Experiment Start Date, the Dataset Creation date is determined by when the data is calibrated and published to the portal. Especially for VBI datasets, this data may lag the Experiment Start Date considerably. It is useful if you want to see the latest data calibrated by the Data Center. Clicking on ADD DATASET CREATION DATE FILTER adds DATASET CREATION DATE RANGE to a user’s current list of selected filters.

2.5.5 Instruments

This filter allows the selection of datasets from one or more of the current DKIST Instruments. This menu is built dynamically so that a user will only be able to choose instruments for which observations have already been taken (Note: VTF will be added in 2026.) As more instruments are commissioned and datasets from them become available, they will appear in the drop-down menu. Clicking ADD INSTRUMENT FILTER adds Instruments to the user’s current list of selected filters.

Figure 16. Selecting instruments to filter by

2.5.6 Spectral Line

This filter allows the selection of datasets by one or more of the spectral lines observed by the DKIST instruments. This is provided as a convenience to the user. Wavelength searches are also available. However, for the VBI, VTF, ViSP and DL-NIRSP instruments, the band-passes in which the instruments observe have already been defined to maximize the scientific return from the instrument. The Spectral Line filter provides an easy way to select these instrument band-passes. For the ViSP instrument, which doesn’t use specific wavebands, a selection of the most common lines has been made. The ViSP line list will be updated as the DC gains more experience with the ViSP wavelengths being searched. For ease of selection, a user can filter by one of the DKIST instruments (i.e., choose Instrument to filter lines) to limit the line selection to that particular instrument. Clicking ADD SPECTRAL FILTER adds Spectral Line to the user’s current list of selected filters.

Figure 17. Selecting the passband or line, in this case from the VBI instrument

See Appendix: Supported Spectral Line Searches for a complete list of the current supported spectral line list.

2.5.7 Spatial

Note that there is a known issue with the WCS headers in both ViSP and VBI calibrated datasets, that will affect the ability to doing spatial / bounding box searches. For observations in the OCP phase a spatial search may return incorrect results or no results at all. For more details, see the https://nso.atlassian.net/wiki/spaces/DDCHD/pages/1959985377 page.

Figure 18. Select data using a spatial filter

This filter allows the selection of datasets using a Spatial Bounding Box. To select a spatial match for datasets, enter the upper and lower corners of a helio-projective cartesian Spatial Bounding Box in arcseconds.

A user may choose a bounds match such that the datasets Contain the bounding box, Intersect the bounding box or are Wholly Contained by the defined box. Effective limit for the bounding box is the maximum off-point for the telescope of ~1.5 RSUN, or -1440” to 1440” in Solar X and -1440” to 1440” in Solar Y. Clicking ADD SPATIAL FILTER allows the user to Add a spatial bounding box to the user’s current list of selected filters.

Figure 19. Illustration of the bounds matches

Figure 19, to the left, illustrates the available bounds matches. The blue rectangle labeled A represents the corners of the observation bounding box. The red rectangles represent the extent of the spatial search bounding box. The red rectangle numbered 1 represents the Wholly Contained match, where the observation bounding box is wholly contained by the spatial search bounding box. The red rectangle numbered 2 represents the Intersects match, where some part of the observation bounding box overlaps the spatial search bounding box. The red rectangle numbered 3 represents the Contains match, where the observation bounding box contains by the spatial search bounding box.

2.5.8 Polarization Observations

This filter allows the selection of datasets depending on whether they contain Polarization Observations. All DKIST instruments except for VBI have the ability to make observations at different polarization angles. Select Polarization Observations Only or Intensity Observations Only to choose between these observations that contain polarimetric data, and those that don’t (Intensity Observations Only). By default (no filter) both observation types (and spectroscopic data) will be selected. Clicking ADD OBSERVATION FILTER allows the user to add Polarization Observations to the user’s current list of selected filters.

Figure 20. Select polarimetric or intensity data
Figure 21. Choose Polarization observations or Intensity observations only. If neither is selected the default is both

 

2.6. Advanced Search Filters

The ‘Advanced’ search filters provide additional filters that may be used to refine the user’s search for DKIST datasets. They are Investigated by Me, Experiment ID, Dataset ID, Numerical wavelength search (primarily for ViSP), Exposure, Fried Parameter, Polarimetric Accuracy, Target Type, If Data Has a Spectral Axis, Spectral sampling, Temporal Sampling and Spatial Sampling. These filters are designed to allow users to locate datasets more quickly, such as if a PI knows their Proposal ID, or has interest in a specific scientific objective, such as a sunspot (Target type) observed with excellent seeing (Fried parameter).

2.6.1 Investigated By Me

Figure 22. Select only datasets for which the logged in user is a PI or Co-I.

This filter quickly allows a principal investigator to find all datasets associated with their login. A user will only see this option if they have logged in via Globus first. Click ADD INVESTIGATED BY ME FILTER to add Investigated By Me to the user’s current list of selected filters.

2.6.2 Experiment ID

Figure 23. Select data by experiment ID(s)

This filter allows the selection of datasets containing a particular Experiment ID. Experiments are how DKIST transforms a proposal into scheduled observing plans. A proposal may contain one or more Experiments. Entering an Experiment ID, e.g., eid_1_50, displays all datasets associated with that ID. To select multiple Experiment IDs, separate them with commas. Attempting to add a new Experiment ID filter when you already have one selected, will just replace the Experiment ID selection with the new one. Note that while all metadata is available for searching, a user will only be able to download data for which they are the PI or a Co-I during the exclusive access period. Clicking ADD EXPERIMENT ID FILTER adds Experiment ID to the user’s current list of selected filters.

2.6.3 Dataset ID

Figure 24. Select data by Dataset ID(s)

This filter allows the selection of datasets containing a particular Dataset ID. For each dataset created by an Experiment, a unique ID, known as the Dataset ID, is assigned. Entering a Dataset ID, e.g., AMJJB, selects a particular dataset. If you add another Dataset ID to the one already selected then both datasets will be returned. Note that while all metadata is available for searching, a user will only be able to download data for which they are the PI or a Co-I during the exclusive access period. Clicking ADD DATASET ID FILTER adds Dataset ID to their current list of selected filters. Users are cautioned that Dataset IDs are only used once. In the event of data reprocessing the Dataset ID will be replaced by a new one. For permanent identifiers to share data with see Product ID below.

2.6.4 Product ID

Screen Shot 2025-07-21 at 10.20.05 PM.png
Figure 25. Select data by Product ID(s)

This filter allows the selection of datasets containing a particular Product ID. For each dataset created by an Experiment, a unique ID, known as the Product ID, is assigned. Entering a Product ID, e.g., L1-JAZXI, selects a particular dataset, in the sameway entering the Dataset ID, LHMMPP,\would. The Product ID, is a new ID created to combat the problem mention above that, Dataset IDs are not conserved through reprocessing. The Product ID will stay the same no matter how many times a dataset is reprocessed. This makes it the ideal ID for sharing datasets with other users. Clicking ADD PRODUCT ID FILTER adds Product ID to the current list of selected filters.

2.6.5 Numerical Wavelength Search (Primarily for ViSP)

Figure 26. Select datasets based on numerical wavelength search

This filter allows the selection of datasets between a minimum and maximum Wavelength. To search on specific wavelengths or wavelength bands, a user enters a minimum and maximum wavelength in nanometers, e.g., 1000nm and 1300nm. Any intersection will match. This is designed to be of particular use for the ViSP instrument. Clicking ADD WAVELENGTH FILTER adds wavelength range (in nm) to a user’s current list of selected filters. Whereas the other DKIST instruments have predefined wavelength bands based on instrument filters, ViSP can image the sun in three bands simultaneously anywhere in the 380‒900 nm range. To search multiple wavelength regimes, add multiple min and max wavelength pairs to your search filters. such as shown in the image below.

Figure 27. Example of searching for multiple wavelengths

2.6.6 Exposure Time

Screen Shot 2025-08-28 at 4.46.47 PM.png
Figure 28. Select datasets by exposure time in milliseconds

This filter allows the selection of datasets based on the minimum and maximum Exposure Time. To filter on Exposure Time, a user enters the minimum and maximum Exposure Times (in milliseconds) to search for datasets. The Exposure times should be common across a dataset. The user may enter either or both of the Exposure bounds. Any intersection will match.

The lower bound will be assumed to be zero if not specified and the upper bound infinite if not specified. Clicking ADD EXPOSURE TIME FILTER adds exposure time range in seconds to a user’s current list of selected filters.

It may appear that some of the returned results do not match your search criteria. This is due to a rounding limitation in which the portal will round the results to the specified precision for the field on display even though the inventory database keeps the data at full precision.

2.6.7 Fried Parameter

Figure 29. Select datasets based on seeing conditions (Fried parameter)

There are no Fried Parameter values available for Cryo-NIRSP. As Cryo-NIRSP takes all the light for its observations currently, the AO system is not running and so no Fried Parameter can be provided.

Should you find that a FITS file is missing an ATMOS_R0 keyword for an instrument other than Cryo-NIRSP, it is because the computed r0 is very likely unreliable. See https://nso.atlassian.net/wiki/spaces/DDCHD/pages/3705897009 for more information.

This filter allows the selection of datasets based on the Fried Parameter. The Fried Parameter (commonly referred to as r0) is a measure of the quality of optical transmission through the atmosphere due to random inhomogeneities in the atmosphere's refractive index. A Fried parameter of 12-15 cm can be considered generally excellent seeing. To filter on the atmospheric seeing conditions, a user enters the minimum Fried parameter (worst seeing) in centimeters (minimum allowed value is 0.1 cm) they are willing to accept. All datasets with a Fried parameter larger (better seeing) than or equal to the minimum Fried parameter will match. Clicking ADD FRIED FILTER adds minimum Fried parameter in centimeters to the user’s current list of selected filters.

2.6.7.1 Caveat

The Fried parameter gives an indication of the atmospheric seeing at a particular moment. The average Fried parameter and its standard deviation are recorded in the dataset Quality Report. While the average Fried parameter can be used as a guide to the seeing quality in a dataset, it should not be done so in isolation and should be considered in conjunction with the values of AO_LOCK and DSHEALTH. It also does not take into account uncommon paths between instruments, or for example instrument vibration which will affect the observed data quality.

2.6.8 Polarimetric Sensitivity (was Accuracy)

 

ChatGPT Image Jan 6, 2026, 02_11_08 PM.png
Figure 30. The Polarimetric Sensitivity (was Accuracy) filter is not currently available.

 

The Polarization Sensitivity (previously mislabeled as Polarimetric Accuracy) filter is not currently available. It was discovered that what was being reported as Polarization Accuracy was never Polarization Accuracy. What should have been reported was the Polarization Sensitivity, however the was calculation for that, was shown to be wrong in the two different places it was being determined as well as the Level 1 headers. An effort is underway to correctly calculate Polarization Sensitivity and correctly display it in all places it should be displayed.

2.6.9 Target Type

Please note that Searches by TargetType do not work because all TargetTypes (taken from the OBJECT keyword) are listed as “unknown”, before observations starting 2023/08/28.

This filter allows the selection of datasets based on the Target Type. Target Type is a designation of the feature type of the observed target as noted by the operators. Target Type is a controlled vocabulary and has values of unknown, quietsun, sunspot, pore, plages, spicules, filament, prominence, coronalhole, quietcorona or activecorona.

Figure 31. Select datasets by known target type

To filter datasets based on Target Type, a user selects one or more of the defined Target Types. All datasets tagged with one of these Target Types will be displayed. Clicking ADD TARGET TYPE FILTER adds target type to a user’s current list of selected filters.

2.6.10 Has Spectral Axis?

Figure 32. Select datasets that have a spectral axis

This filter allows the selection of datasets based on whether the dataset contains a spectral axis. This will include both spectroscopic and spectrapolarimetric data. Only datasets that contain a Spectral Axis will be displayed when selected. Clicking ADD HAS A SPECTRAL AXIS FILTER adds Has Spectral Axis to a user’s current list of selected filters.

2.6.11 Spectral Sampling

Figure 33. Select datasets based on spectral sampling