arogozhnikov

5 ms·

1.
by arogozhnikov 3y ago
> But these computation graphs are similar every time. For now I'm testing one-after-another because failure of previous (overflow, too-small-transfer, etc) gives a hint about which part can be changed in the graph. I've been t
2.
by arogozhnikov 3y ago
Robotic planning of liquid handling. There are many potential alternative ways to achieve the same result, each resulting in its own computation graph. I imagine any kind of trajectory planning for many agents faces similar challenges (e.g.
3.
by arogozhnikov 4y ago
same for me
4.
by arogozhnikov 6y ago
sums it up pretty well
5.
by arogozhnikov 6y ago
> API != User Interface. API = Programming Interface. That's where we should start, but the other way around. Why do you keep trying to replace programming interfaces with bash calls? Any example when calling cli compared to propos
6.
by arogozhnikov 6y ago
> then it should be pretty easy to test. If it is that simple, you can just devote this to package like typer. That's what I point to - don't write it. I see people somehow read GUI along the lines, while I never even considere
7.
by arogozhnikov 6y ago
ok, I understand now my question got misinterpreted, I'll rewrite that. CLI parsing (mapping to real calls) may have bugs. How do you test this? Both options suggested eliminate this possibility completely. > one of their core advan
8.
by arogozhnikov 6y ago
+1 for reading post
9.
by arogozhnikov 6y ago
> Agree the CLI "shell" around the system should not have separate logic that was the main point. > should report back logic faults from within the library And I suggest validating parameters passed to functions. So what&#x2
10.
by arogozhnikov 6y ago
It looks new - but is it any more complicated if after all that's what your call maps to?
11.
by arogozhnikov 6y ago
It is easy only if you write CLI utility (or somewhat very light-weight). Imagine you write ASR system (from CLI input to output - week(s) of training, requires several servers). Mind telling me more about using diff/stdin/stdout
12.
Don't write command-line interfaces (and how to write if you have to)(arogozhnikov.github.io)
13 points by arogozhnikov 6y ago|24 comments
13.
Migrating to Python 3 with pleasure(github.com)
320 points by arogozhnikov 9y ago|176 comments
14.
Reconstructing pictures with machine learning (demo)(arogozhnikov.github.io)
1 points by arogozhnikov 9y ago|0 comments
15.
Jupyter (IPython) notebooks features(arogozhnikov.github.io)
6 points by arogozhnikov 10y ago|0 comments
16.
by arogozhnikov 10y ago
+1ed the issue. I was sure that's a problem on Safari side.