-
We've informally discussed having a standard library, namely for [supporting ZKPs](#14 ) but there are other utilities that we should support by default.
Some basic ideas:
- Differential privacy uti…
-
I'm starting to get to the point where I have a lot of cypress component tests.
It's about time I start finding patterns, and start standardizing.
The Commit for Create User Profile would be a goo…
-
-
There are metadata standards for geospatial data like ISO 19115-2. At a minimum, we could peruse this for ideas about what goes in the catalog and what metadata need to be passed along to the user.
…
-
First of all, thank you for all of your amazing image work!
It looks like Chrome 91 (current beta) is requiring extra format compatibility for AVIF files. Images generated by [cavif](https://github…
-
A list of standard samples run regularly on beamlines should be created.
This could potentially link with the discussion in issue #3.
arm61 updated
3 years ago
-
1. Config File where we can update username database name should be single.
2. Don't make connection again and again
3. Database commands should be at one place at expend if possible
-
We should create some rules to coding since we have some unspoken rules. We have a `clang-format` to take care about formatting. IMO the following rules should be explicit for newer contributions
1…
-
We should consider adding a few standard splitters with automatic shuffling:
- `split_train_test(ratio=[0.8,0.2])`
- `split_train_val_test(ratio=[0.65,0.15,0.2])`
- `split_k_fold(k=5)`
- `split_ba…
-
Would you be open to a PR that adds support for .NET Standard, in addition to the existing platforms?
We'd like to use SharpFont in the [OpenSAGE](https://github.com/OpenSAGE/OpenSAGE) project, whi…