You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 2016/ideas-list-dynd.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,10 @@
18
18
19
19
Complete DyND's string type implementation and develop the supporting string library. Explore how string processing and NumPy-style array programming interact.
| Moderate || Irwin Zaid, Mark Wiebe, Ian Henriksen |
24
+
21
25
### Technical Details
22
26
23
27
DyND's string type and supporting library are incomplete. A project could involve completing the implementation of the basic string type, fleshing out the supporting string function API, connecting DyND strings to the Numba JIT, and exploring how string API choices interact with the array programming ideas and typical data ingest and analysis workflows.
@@ -44,6 +48,10 @@ C\++ development experience, particularly with C\++11 or C\++14, is necessary. F
44
48
45
49
Implement binary serialization for DyND array data, and corresponding data hashing that's useful for building Merkle DAG-based systems.
| Moderate || Irwin Zaid, Mark Wiebe, Ian Henriksen |
54
+
47
55
### Technical Details
48
56
49
57
DyND's nd::array object can store many forms of data in memory. Being able to generically serialize these objects into blobs of bytes for saving on disk or transporting across a network is needed for many use cases. DyND's design aims to use an obvious raw-style format for the serialized data, to be usable as a building block for more sophisticated systems.
@@ -74,6 +82,10 @@ A project tackling this functionality could begin with implementing the serializ
74
82
75
83
Implement an associative array type for DyND as a hash map.
This idea overlaps slightly with [Serialization and Data Hashing](#serialization), but focuses on the implementation of a hash map type instead of the hashing its built on. The idea would be for the type to be named like `map[S, T]`, and be a hash table with keys of type `S` and values of type `T`.
@@ -102,6 +114,10 @@ C\++ development experience, particularly with C\++11 or C\++14, is necessary. A
102
114
103
115
Improve DyND's support for missing data via its `option[T]` type, targetting DyND's ability to be used by projects like [pandas](http://pandas.pydata.org/).
Having a representation for missing data and ways to meaningfully manipulate them are crucial for data analytics applications. DyND has preliminary support for this, but it is far from complete.
@@ -134,6 +150,10 @@ C\++ development experience, particularly with C\++11 or C\++14, is necessary. E
134
150
135
151
Integrate robust conversions of float point values to/from strings.
As part of being a library to facilitate interoperability of data, DyND needs to include good quality routines for conversion of floating point values to and from strings. This basic functionality is used by I/O such as for JSON and CSV, and in displaying output for the user or interpreting user input.
0 commit comments