developers.lco.globalLCO Developers
developers.lco.global Profile
developers.lco.global
Maindomain:lco.global
Title:LCO Developers
Description:NAV Python Javascript Introduction Example usage and code samples will appear on this column. Choose which language you’d like to view from the menu at the top. Python examples assume requests is in
Discover developers.lco.global website stats, rating, details and status online.Use our online tools to find owner and admin contact info. Find out where is server located.Read and write reviews or vote to improve it ranking. Check alliedvsaxis duplicates with related css, domain relations, most used words, social networks references. Go to regular site
developers.lco.global Information
Website / Domain: |
developers.lco.global |
HomePage size: | 205.185 KB |
Page Load Time: | 0.235721 Seconds |
Website IP Address: |
54.244.35.13 |
Isp Server: |
Amazon.com Inc. |
developers.lco.global Ip Information
Ip Country: |
United States |
City Name: |
Portland |
Latitude: |
45.523448944092 |
Longitude: |
-122.67620849609 |
developers.lco.global Keywords accounting
developers.lco.global Httpheader
Date: Sat, 29 Feb 2020 10:56:02 GMT |
Content-Type: text/html |
Transfer-Encoding: chunked |
Connection: keep-alive |
Server: nginx/1.17.7 |
Vary: Accept-Encoding |
Last-Modified: Fri, 20 Dec 2019 07:21:20 GMT |
ETag: W/"5dfc7670-2a9fd" |
Content-Encoding: gzip |
developers.lco.global Meta Info
content="Hugo 0.20.6" name="generator"/ |
charset="utf-8"/ |
content="IE=edge,chrome=1" http-equiv="X-UA-Compatible"/ |
content="width=device-width, initial-scale=1, maximum-scale=1" name="viewport"/ |
54.244.35.13 Domains
developers.lco.global Similar Website
Domain |
WebSite Title |
developers.lco.global | LCO Developers |
asteroidtracker.lco.global | Asteroid Tracker powered by LCO |
microlensing.lco.global | microlensing.lco.global - Index page |
devblogs.nvidia.com | NVIDIA Developer Blog | Technical content: For developers, by developers |
naiknavare.com | Real Estate Builders and Developers in Pune | Naiknavare Developers |
developers.pipelinersales.com | Developers - Developers |
mapserve.utah.gov | Developers |
mapserv.utah.gov | Developers |
developers.nest.com | Nest Developers |
developer.mbta.com | Developers | MBTA |
developer.mastercard.com | Mastercard Developers |
developers.facebook.com | Facebook for Developers |
api.census.gov | Developers - Census |
developers.yubico.com | Yubico Developers |
developers.messagebird.com | MessageBird for Developers |
developers.lco.global Traffic Sources Chart
developers.lco.global Alexa Rank History Chart
developers.lco.global Html To Plain Text
NAV Python Javascript Introduction Example usage and code samples will appear on this column. Choose which language you’d like to view from the menu at the top. Python examples assume requests is installed. Javascript assumes the use of jQuery Welcome to the LCO Developer documentation! Here you will find API documentation, sample code, tutorials and other resources to aid your development with LCO services. A note about code formatting An ellipses ... acts as a placeholder for additional data that would otherwise take up too much space. These will not appear in actual API requests or responses. For example, an endpoint that returns the data: { "target": { "type": "SIDEREAL", "name": "m42", "ra": 83.8220792, "dec": -5.3911111, "proper_motion_ra": 1.67, "proper_motion_dec": -0.3, "parallax": 0.0, "coordinate_system": "ICRS", "equinox": "J2000", "epoch": 2000.0, }, } May be shortened in the documentation to: { "target": { ... "type": "SIDEREAL", "name": "m42", ... } } Information relevant to the documentation being described will always be shown. All dates are in UTC and all date fields are in the ISO 8601 format. Deprecation Policy LCO wants to make sure we provide a consistent, performant interface to our network services. When a public API must undergo a breaking change, we will make our best effort to notify all consumers. When applicable, APIs will be versioned to provide ample time for clients to adapt. Old versions will stay supported for at least 3 months and can be accessed using a different URL. Example: https://observe.lco.global/api/v2/ LCO will provide documentation at developers.lco.global in order to make API transitions as easy as possible. Paginating Results Any LCO api which returns a list of potentially many results will be paginated. The default limit is usually 100 but may vary based on the type of data being returned. Results can be iterated on using the limit and offset query parameters. For example, if your query result count is 2200, you can make 3 queries to access all the results: limit=1000&offset=0 limit=1000&offset=1000 limit=1000&offset=2000 Observations Api root: https://observe.lco.global/api Overview The observations API provides endpoints for submitting and querying observation requests. Observation requests cannot be edited once they are submitted, but they can be canceled. You may follow their statuses using endpoints outlined below. Practical examples on how to use this API are provided by scripts linked from the code samples section. Rate Limits The observations API is rate limited in order to remain available to all users in the event that a single user attempts to make too many requests in too rapid a succession, causing denial of service to other clients. Data Format Definition Observation Request Model Structure Observation requests follow a hierarchical structure as shown in the diagram below: RequestGroup The top level entity in the LCO request language is the RequestGroup . A RequestGroup contains one or more Request s and acts as a logical grouping to help the end user keep track of a set of Request s. All observing requests are submitted within this top level struture. A sample RequestGroup returned via the API: { "id" : 12345 , "submitter" : "austin_riba" , "requests" : [ ... ], "name" : "Test observation" , "observation_type" : "NORMAL" , "operator" : "SINGLE" , "ipp_value" : 1.05 , "state" : "PENDING" , "proposal" : "LCOEngineering" } Field Read Only Required Options Description id true false The id of this RequestGroup . requests false true The list of Request s to be observed for this RequestGroup . submitter true false The user that submitted the RequestGroup . proposal false true The Proposal under which this observation will be made. name false true A string placed in the FITS header as the GROUPID keyword value for all FITS frames originating from this RequestGroup . observation_type false true NORMAL, RAPID_RESPONSE, TIME_CRITICAL The type of observation. A proposal must be granted time specifically for each observation type. More information can be found here . operator false true SINGLE, MANY Use SINGLE if you have only one Request , and MANY if you have more than one. ipp_value false true A multiplier (from 0.5 to 2.0, generally set to 1.05) to your Proposal ’s base priority value for this RequestGroup and all of its child Request s. A value > 1.0 will raise your priority and debit your Proposal âs ipp_time_available upon submission. If a Request does not complete, the time debited for that Request is returned. A value < 1.0 will lower your priority and credit your Proposal âs ipp_time_available up to your ipp_limit on the successful completion of a Request . For more information on IPP, see here . Note that ipp time only applies to NORMAL observation_type requests. state true false PENDING, WINDOW_EXPIRED, COMPLETED, CANCELED The current state of this RequestGroup . Request A sample Request returned via the API: { "id" : 4 , "location" : { ... }, "configurations" : [ ... ], "windows" : [ ... ], "observation_note" : "" , "state" : "PENDING" , "acceptability_threshold" : 90 } A Request is a single independent set of observations to be scheduled in one contiguous block on a resource. Field Read Only Required Options Description id true false The id of this Request . location false true The Location from which this Request should be observed. configurations false true A list of Configuration s. windows false true A list of Window s in which this Request should be considered for observation. observation_note false false Text describing this Request . acceptability_threshold false false The percentage of the observation that must be completed to mark the request as complete and avert rescheduling. The percentage should be set to the lowest value for which the amount of data is acceptable to meet the science goal of the request. Defaults to 100 for FLOYDS observations and 90 for all other observations. state true false PENDING, WINDOW_EXPIRED, COMPLETED, CANCELED The current state of this Request . Location A sample location returned via the API: { "telescope_class" : "2m0" } A Location specifies a set of restrictions on which resources the Request can be scheduled. Field Read Only Required Options Description telescope_class false true 0m4, 0m8, 1m0, 2m0, 4m0 The telescope class which will be used for this observation. The class describes the aperture size, i.e. 1m0 is a 1m telescope, and 0m4 is a 0.4m telescope. Window A sample window returned via the API: { "start" : "2017-3-22 14:26:08" , "end" : "2017-3-22 14:26:08" } A Window specifies one or more datetime intervals during which the Request can be observed. The visibility calculator might be helpful in deciding a window for your observation. Field Read Only Required Description start false true The time when the observing window starts. end false true The time when the observing window ends. Configuration A sample configuration returned via API: { "type" : "EXPOSE" , "instrument_type" : "2M0-SCICAM-SPECTRAL" , "instrument_configs" : [ ... ], "acquisition_config" : { ... }, "guiding_config" : { ... }, "constraints" : { ... }, "target" : { ... } } A sample repeat configuration returned via API: { "type" : "REPEAT_EXPOSE" , "instrument_type" : "2M0-SCICAM-SPECTRAL" , "repeat_duration" : 1500.0 , "instrument_configs" : [ ... ], "acquisition_config" : { ... }, "guiding_config" : { ... }, "constraints" : { ... }, "target" : { ... } } A Configuration defines the configuration for a set of observations on a single Target . Field Read Only Required Options Description type false true EXPOSE, REPEAT_EXPOSE, SPECTRUM, REPEAT_SPECTRUM, NRES_SPECTRUM, REPEAT_NRES_SPECTRUM, LAMP_FLAT, ARC, STANDARD The type of exposure. instrument_type false true 1M0-SCICAM-SINISTRO, 2M0-SCICAM-SPECTRAL, 0M4-SCICAM-SBIG, 2M0-FLOYDS-SCICAM, 1M0-NRES-SCICAM, SOAR_GHTS_REDCAM, SOAR_GHTS_REDCAM_IMAGER The type of instrument. repeat_duration false false ...
developers.lco.global Whois
"domain_name": [
"LCO.GLOBAL",
"lco.global"
],
"registrar": "GoDaddy.com, LLC",
"whois_server": "whois.godaddy.com",
"referral_url": null,
"updated_date": [
"2017-06-23 18:01:01",
"2017-06-23 18:00:59"
],
"creation_date": "2016-08-22 22:15:57",
"expiration_date": "2020-08-22 22:15:57",
"name_servers": [
"NS-881.AWSDNS-46.NET",
"NS-1402.AWSDNS-47.ORG",
"NS-1568.AWSDNS-04.CO.UK",
"NS-380.AWSDNS-47.COM"
],
"status": [
"clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited",
"clientRenewProhibited https://icann.org/epp#clientRenewProhibited",
"clientTransferProhibited https://icann.org/epp#clientTransferProhibited",
"clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited",
"clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited",
"clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited",
"clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited",
"clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited"
],
"emails": "abuse@godaddy.com",
"dnssec": "unsigned",
"name": null,
"org": null,
"address": null,
"city": null,
"state": "California",
"zipcode": null,
"country": "US"