haptork

22 ms·

1. 1.▲
   by haptork 7y ago

   Nice article. We recently used t-SNE and UMAP in the field of radiation damage, for visualising the damage shapes (point defect clusters of different shapes). The results were interesting in many ways. We found that the general layout of cl
2. 2.▲
   by haptork 10y ago

   Thanks! corrected.
3. 3.▲
   Ezl, Spark, MPI Experiments on HPC, EC2 and Multicore(haptork.github.io)

   3 points by haptork 10y ago|2 comments
4. 4.▲
   Easy Unary Predicates(haptork.github.io)

   1 points by haptork 10y ago|0 comments
5. 5.▲
   by haptork 11y ago

   If you can give some idea of the client code / API that you are expecting, I might be able to give some view on that.
6. 6.▲
   by haptork 11y ago

   Thanks for your interest. There are indeed no function pointers, no void pointers, no preprocessor hacks, no wild type-casting involved anywhere in the library. This is completely compile time type-safe. Still, the kind of things you can do
7. 7.▲
   by haptork 11y ago

   Yeah, you are right, fault tolerance is a needed feature. Although, I'm not pretty sure if that needs to be added to easyLambda itself. Since, MPI 3.0 is expected to support fault tolerance by default. But instead of waiting for MPI 3.
8. 8.▲
   by haptork 11y ago

   One can still use TBB inside the functions to make use of it alongside getting MPI parallelism from easyLambda. Moreover, easyLambda has data flows, map, reduce which in a way improves the way programs are written and composed. There are no
9. 9.▲
   by haptork 11y ago

   Here is an article around this style (ExpressionBuilder) by martin fowler: http://martinfowler.com/bliki/ExpressionBuilder.html