Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: butler
-
Labels:None
-
Story Points:15
-
Epic Link:
-
Team:Data Access and Database
Description
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like:
create a skymap object given a configuration (in the repository) (it has its own dataset type)
create a registry with that skymap object
use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap.
requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap.
example use case:
{
|
datasetType = 'coaddTempExp'
|
key = (?)
|
format = ['patch', 'visit']
|
dataId = {'tract':<some numberOrId>}
|
myButler.queryMetadata(datasetType, key, format, dataId)
|
}
|
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | butler [ 12317 ] | |
Team | Data Access and Database [ 10204 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Description |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {{datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId)}} |
Description |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {{datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId)}} |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {{datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId) }} |
Description |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {{datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId) }} |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {{ datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId) }} |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13228 ] | This issue links to "Page (Confluence)" [ 13228 ] |
Rank | Ranked higher |
Remote Link | This issue links to "Page (Confluence)" [ 13256 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13256 ] | This issue links to "Page (Confluence)" [ 13256 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13256 ] | This issue links to "Page (Confluence)" [ 13256 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13256 ] | This issue links to "Page (Confluence)" [ 13256 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13256 ] | This issue links to "Page (Confluence)" [ 13256 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Description |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {{ datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId) }} |
load the skymap from the repository and use it a la metadata lookup to complete lookups. for example if the script wants all the patches that are in tract x, look in the skymap to get that information.
will be something like: create a skymap object given a configuration (in the repository) (it has its own dataset type) create a registry with that skymap object use that registry to lookup skymap related parameters. Might need to add to the policy file that a given configuration uses the skymap. requires that data is already indexable by tract & patch, the work is adds iteration over tract/patch specified by the skymap. example use case: {code} { datasetType = 'coaddTempExp' key = (?) format = ['patch', 'visit'] dataId = {'tract':<some numberOrId>} myButler.queryMetadata(datasetType, key, format, dataId) } {code} |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Epic Link | DM-4341 [ 21422 ] |
Story Points | 15 |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked higher |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Rank | Ranked higher |
Rank | Ranked higher |
Remote Link | This issue links to "Page (Confluence)" [ 13260 ] | This issue links to "Page (Confluence)" [ 13260 ] |
Rank | Ranked lower |
Epic Link | DM-4341 [ 21422 ] | DM-6047 [ 24358 ] |
Epic Link | DM-6047 [ 24358 ] | DM-4341 [ 21422 ] |
Epic Link | DM-4341 [ 21422 ] | DM-6047 [ 24358 ] |
Epic Link | DM-6047 [ 24358 ] |
|
Sprint | DB_S17_12 [ 304 ] |
Sprint | DB_S17_12 [ 304 ] | DB_S17_01 [ 307 ] |
Rank | Ranked higher |
Rank | Ranked lower |
Sprint | DB_S17_01 [ 307 ] |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked higher |
Remote Link | This issue links to "Page (Confluence)" [ 29416 ] |
Resolution | Done [ 10000 ] | |
Status | To Do [ 10001 ] | Won't Fix [ 10405 ] |
I don't think we can get away with hard-coding the skymap configuration in the mapper policy file, at least as those policy files stand now; each camera needs to be able to support multiple skymap configurations (though not within the same data repository).