forked from HDFGroup/hdf5
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement support for Complex number datatypes #6
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
3 times, most recently
from
June 7, 2024 00:15
a775586
to
7f7334b
Compare
Sites like GitLab can have internal problems that return http 500 errors while they fix their problems. Some sites also return http 200 OK, which is fine. This PR adds a config file to the markdown link check so those are considered "passing" and don't break the CI.
These examples are referred to from the replacement page of https://portal.hdfgroup.org/display/HDF5/Other+Examples.
* Correct property cb signatures in docs * Correct delete callback type name in docs * add missing word to H5P__free_prop doc
* off_t --> HDoff_t in test * off_t --> HDoff_t in h5ls, h5dump, & h5repack * Minor off_t tweak to configure.ac * off_t --> HDoff_t fixes in src This changes the type of the offset parameter in H5Pget_external() to HDoff_t to match H5Pset_external(), along with other minor tweaks. * off_t --> HDoff_t in C++ wrappers * Fix off_t usage in Java wrapper
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
2 times, most recently
from
June 10, 2024 23:30
bd23c3a
to
61721bd
Compare
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
from
June 12, 2024 15:28
d136f71
to
729325f
Compare
We don't test parallel in other GitHub actions, so this also converts the NVHPC check to configure and build only while we discuss how we'll test parallel HDF5 in GitHub. There is a blocking GitHub issue to address the test failures for HDF5 1.14.5 (HDFGroup#4571).
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
3 times, most recently
from
June 18, 2024 05:20
a3d6e6e
to
7ac1403
Compare
* Removes printf debugging * Simplifies and centralizes stats code * Use #ifdef ROS3_STATS instead of #if * Other misc tidying
Not a new change - an artifact from a previous check-in.
…4475) An internal capability that's similar to the H5E_BEGIN_TRY / H5E_END_TRY macros in H5Epublic.h, but more efficient since we can avoid pushing errors on the stack entirely (and those macros use public API routines). This capability (and other techniques) can be used to remove use of H5E_clear_stack() and H5E_BEGIN_TRY / H5E_END_TRY within library routines. We want to remove H5E_clear_stack() because it can trigger calls to the H5I interface from within the H5E code, which creates a great deal of complexity for threadsafe code. And we want to remove H5E_BEGIN_TRY / H5E_END_TRY's because they make public API calls from within the library code. Also some other minor tidying in routines related to removing the use of H5E_clear_stack() and H5E_BEGIN_TRY / H5E_END_TRY from H5Fint.c
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
* Correct comment for H5CX_get_data_transform * Document why data transform ctx field doesnt use macro
* Removed JS* macro scheme (replaced w/ h5test.h macros) * Moved curl setup/teardown to main() * A lot of cleanup and simplification
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
3 times, most recently
from
June 19, 2024 18:46
16daa29
to
d6e53f3
Compare
* H5FD_s3comms_nlowercase() * H5FD_s3comms_trim() * H5FD_s3comms_uriencode()
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
from
June 19, 2024 19:34
d6e53f3
to
9558d70
Compare
jhendersonHDF
force-pushed
the
feature/complex_number_support
branch
5 times, most recently
from
June 20, 2024 20:45
f495638
to
9dd8bc9
Compare
replace usages of word "complex" to distinguish from complex datatypes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace usages of word "complex" to distinguish from complex datatypes