[jira] [Created] (SDAP-502) Tile generation fails for slices with single lats or lons
Riley Kuttruff created SDAP-502: --- Summary: Tile generation fails for slices with single lats or lons Key: SDAP-502 URL: https://issues.apache.org/jira/browse/SDAP-502 Project: Apache Science Data Analytics Platform Issue Type: Bug Components: granule-ingester Reporter: Riley Kuttruff Assignee: Riley Kuttruff Data subsetting in the tile reading processor uses np.squeeze on subsetted data ([example|[https://github.com/apache/incubator-sdap-ingester/blob/0589f473c66a68830aca4b06160f8e756459e4f6/granule_ingester/granule_ingester/processors/reading_processors/GridReadingProcessor.py#L35-L42]).] In the event that a tile is one greater than a multiple of the desired tile size (eg, dim length mod dim tile length == 1), we will get a lat or lon subset whose dimension lengths are all 1. When that is squeezed, the result is a 0-dimension numpy array, which can then throw an error, say, it it is used as an input to len(). A simple fix would be to check if the squeezed subset is 0-dimensional and then expanding it into a dimensioned array. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SDAP-502) Tile generation fails for slices with single lats or lons
[ https://issues.apache.org/jira/browse/SDAP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riley Kuttruff reassigned SDAP-502: --- Assignee: (was: Riley Kuttruff) > Tile generation fails for slices with single lats or lons > - > > Key: SDAP-502 > URL: https://issues.apache.org/jira/browse/SDAP-502 > Project: Apache Science Data Analytics Platform > Issue Type: Bug > Components: granule-ingester >Reporter: Riley Kuttruff >Priority: Trivial > > Data subsetting in the tile reading processor uses np.squeeze on subsetted > data > ([example|[https://github.com/apache/incubator-sdap-ingester/blob/0589f473c66a68830aca4b06160f8e756459e4f6/granule_ingester/granule_ingester/processors/reading_processors/GridReadingProcessor.py#L35-L42]).] > In the event that a tile is one greater than a multiple of the desired tile > size (eg, dim length mod dim tile length == 1), we will get a lat or lon > subset whose dimension lengths are all 1. When that is squeezed, the result > is a 0-dimension numpy array, which can then throw an error, say, it it is > used as an input to len(). > > A simple fix would be to check if the squeezed subset is 0-dimensional and > then expanding it into a dimensioned array. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[QUESTION] IP-Clearance and Name Search
I wanted to check if we're clear with the IP Clearance tasks in regards to the main body of SDAP code. The documentation on Incubator's website [1] has me a little confused as to if this process is necessary/the correct one for the initial codebase, as opposed to contributing additional large portions of code to the SDAP podling; I've committed an XML file for the main SDAP code just in case [2]. As for the name search, I opened the ticket a few days ago [3] and am curious how long the process should be expected to take. Thanks, Riley [1] https://incubator.apache.org/ip-clearance/ip-clearance-template.html [2] https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/sdap.xml [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-216
