drms icon indicating copy to clipboard operation
drms copied to clipboard

Access HMI, AIA and MDI data with Python from public JSOC DRMS servers

Results 13 drms issues
Sort by recently updated
recently updated
newest added

### Provide a general description of the issue or problem. TIme to move to pyproject and ruff for everything.

Made StrEnum to avoid the `.value` call This is a breaking change and will not be backported.

Currently the examples written in the ``examples/`` folder could do with major copy editing. Ideally we would want more introduction text to explain what is going in, probably remove some...

Feature Request

### Provide a general description of the issue or problem. The JSOC are planning to return the download URL in the upcoming export system refresh. When this is done, we...

Feature Request

### Here's the current behavior: ```python >>> import drms >>> email = '[email protected]' >>> client = drms.Client(email=email) >>> hmi_query_string = 'hmi.sharp_cea_720s[377][2011.02.15_02:12:00_TAI]' >>> r = client.export(hmi_query_string+'{Br}', protocol='fits', email=email) export URL: http://jsoc.stanford.edu/cgi-bin/ajax/jsoc_fetch?op=exp_request&format=json&ds=hmi.sharp_cea_720s%5B377%5D%5B2011.02.15_02%3A12%3A00_TAI%5D%7BBr%7D&notify=thomas.berger%40colorado.edu&method=url&protocol=fits&filenamefmt=hmi.sharp_cea_720s.%7BHARPNUM%7D.%7BT_REC%3AA%7D.%7Bsegment%7D&process%3Dn=0&requestor=thomas.berger&sizeratio=1.0...

Bug

### Description When making URL requests via the DRMS Client class, network connections do not timeout and fail gracefully. This leads to requests such as "query", "export", and "download" to...

Bug

So it looks like drms is interpreting the quality flag as unsigned int but the backend service views it as a signed 32 bit int. ```python from drms.client import Client...

Add a `wcskeys` parameter to `drms.Client.query()` which selects all WCS keywords that are available for the queried series (similar to the already existing `pkeys` parameter).

Feature Request

The `Client.query()` method currently only returns segment locations. It would be useful in some cases to also have access to additional by-record segment information (like image dimensions) using the public...

Feature Request