Skip to content

Commit 698e15f

Browse files
committed
Add difficulty rating/mentors list to dynd ideas list
1 parent e546dc1 commit 698e15f

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

2016/ideas-list-dynd.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@
1818

1919
Complete DyND's string type implementation and develop the supporting string library. Explore how string processing and NumPy-style array programming interact.
2020

21+
| **Intensity** | **Involves** | **Mentors** |
22+
| ------------- | --------------|------------------- |
23+
| Moderate | | Irwin Zaid, Mark Wiebe, Ian Henriksen |
24+
2125
### Technical Details
2226

2327
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
4448

4549
Implement binary serialization for DyND array data, and corresponding data hashing that's useful for building Merkle DAG-based systems.
4650

51+
| **Intensity** | **Involves** | **Mentors** |
52+
| ------------- | --------------|------------------- |
53+
| Moderate | | Irwin Zaid, Mark Wiebe, Ian Henriksen |
54+
4755
### Technical Details
4856

4957
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
7482

7583
Implement an associative array type for DyND as a hash map.
7684

85+
| **Intensity** | **Involves** | **Mentors** |
86+
| ------------- | --------------|------------------- |
87+
| Hard | | Irwin Zaid, Mark Wiebe, Ian Henriksen |
88+
7789
### Technical Details
7890

7991
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
102114

103115
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/).
104116

117+
| **Intensity** | **Involves** | **Mentors** |
118+
| ------------- | --------------|------------------- |
119+
| Hard | | Irwin Zaid, Mark Wiebe, Ian Henriksen |
120+
105121
### Technical Details
106122

107123
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
134150

135151
Integrate robust conversions of float point values to/from strings.
136152

153+
| **Intensity** | **Involves** | **Mentors** |
154+
| ------------- | --------------|------------------- |
155+
| Hard | | Irwin Zaid, Mark Wiebe, Ian Henriksen |
156+
137157
### Technical Details
138158

139159
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

Comments
 (0)