-
Notifications
You must be signed in to change notification settings - Fork 16
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: fhs/pyhdf
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.11.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: fhs/pyhdf
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 19 commits
- 14 files changed
- 6 contributors
Commits on Jun 25, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 67beb1c - Browse repository at this point
Copy the full SHA 67beb1cView commit details
Commits on Aug 12, 2023
-
Fix reads of 8-bit signed char SDSs (#68)
This fixes an issue encountered after a recent upgrade from pyhdf 0.10.5 to 0.11.3. When reading an SDS of type `SDC.CHAR` with version 0.11.3, I'd get the following error: ``` In [2]: SD("MYD03.A2023213.0000.061.2023213152719.hdf").select("Scan Type").get() --------------------------------------------------------------------------- ValueError Traceback (most recent call last) Cell In[2], line 1 ----> 1 SD("MYD03.A2023213.0000.061.2023213152719.hdf").select("Scan Type").get() File ~/Code/pyhdf/pyhdf/SD.py:1920, in SDS.get(self, start, count, stride) 1916 if not data_type in SDC.equivNumericTypes: 1917 raise HDF4Error('get cannot currently deal with '\ 1918 'the SDS data type') -> 1920 return _C._SDreaddata_0(self._id, data_type, start, count, stride) File ~/Code/pyhdf/pyhdf/hdfext.py:333, in _SDreaddata_0(sds_id, data_type, start, edges, stride) 332 def _SDreaddata_0(sds_id, data_type, start, edges, stride): --> 333 return _hdfext._SDreaddata_0(sds_id, data_type, start, edges, stride) ValueError: data type must provide an itemsize ``` I tracked the problem down to use of `PyArray_SimpleNew` with typenum `NPY_STRING`, which fails because that type code requires a size specification. This change instead uses `PyArray_New` with an `itemsize` of 1, which reproduces the 0.10.5 `SDC.CHAR` read behavior. All the non-`NPY_STRING` type codes are fixed-size in which case `PyArray_New` ignores the `itemsize` argument so behavior for these type codes should be unaffected. Fixes #67 --------- Co-authored-by: Greg Quinn <greg.quinn@ssec.wisc.edu>Configuration menu - View commit details
-
Copy full SHA for e8f87ad - Browse repository at this point
Copy the full SHA e8f87adView commit details
Commits on Mar 14, 2024
-
Check Multi-Arch path to fix build on Debian. (#71)
The Debian package failed to build as reported in [Debian Bug #1066395](https://bugs.debian.org/1066395). This is fixed by also searching the [MultiArch](https://wiki.debian.org/Python/MultiArch#Python_code) path for the hdf4alt libraries.
Configuration menu - View commit details
-
Copy full SHA for f508ec8 - Browse repository at this point
Copy the full SHA f508ec8View commit details -
Configuration menu - View commit details
-
Copy full SHA for e26afc7 - Browse repository at this point
Copy the full SHA e26afc7View commit details
Commits on Jun 20, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 7746b03 - Browse repository at this point
Copy the full SHA 7746b03View commit details
Commits on Oct 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 5dab15c - Browse repository at this point
Copy the full SHA 5dab15cView commit details
Commits on Jan 4, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 79be7e5 - Browse repository at this point
Copy the full SHA 79be7e5View commit details
Commits on Jan 5, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c452b29 - Browse repository at this point
Copy the full SHA c452b29View commit details -
Configuration menu - View commit details
-
Copy full SHA for c048200 - Browse repository at this point
Copy the full SHA c048200View commit details -
Configuration menu - View commit details
-
Copy full SHA for cb447e4 - Browse repository at this point
Copy the full SHA cb447e4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2107fb7 - Browse repository at this point
Copy the full SHA 2107fb7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9f5e0b0 - Browse repository at this point
Copy the full SHA 9f5e0b0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8ae76ad - Browse repository at this point
Copy the full SHA 8ae76adView commit details -
Configuration menu - View commit details
-
Copy full SHA for 18b45ff - Browse repository at this point
Copy the full SHA 18b45ffView commit details -
Configuration menu - View commit details
-
Copy full SHA for c704d58 - Browse repository at this point
Copy the full SHA c704d58View commit details -
Configuration menu - View commit details
-
Copy full SHA for 82bb6bc - Browse repository at this point
Copy the full SHA 82bb6bcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6de48b3 - Browse repository at this point
Copy the full SHA 6de48b3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8d1a8ca - Browse repository at this point
Copy the full SHA 8d1a8caView commit details -
Configuration menu - View commit details
-
Copy full SHA for 12376cf - Browse repository at this point
Copy the full SHA 12376cfView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.11.3...master