allenofthehills

Marker placement in motion capture is often intentionally bilaterally asymmetric because it makes automatic labeling of markers easier (with respect to side/orientation of the subject).

Source: Am a biomechanist with several years of mocap experience.

This is a common misconception, but you are actually talking about "replicability" which is "writing and then running new software based on the description of a computational model or method provided in the original publication, and obtaining results that are similar enough" [1]. Reproducibility instead refers to running the same code on the same data to get the same results [2].

[1] Rougier et al., "Sustainable computational science: the ReScience initiative" https://arxiv.org/abs/1707.04393

[2] Plesser, "Reproducibility vs. Replicability: A Brief History of a Confused Terminology" https://doi.org/10.3389/fninf.2017.00076

> The software was "reproducible" in that the same starting conditions produced the same output, but that didn't mean the _science_ was reproducible, as every study used the same software.

This is the difference between reproducibility and replicability [1]. Reproducibility is the ability to run the same software on the same input data to get the same output; replication would be analyzing the same input data (or new, replicated data following the original collection protocol) with new software and getting the same result.

I've experienced the same lack of interest with established researchers in my field, but I can at least ensure that all my studies are both reproducible and replicable by sharing my code and data.

[1] Plesser HE. Reproducibility vs. Replicability: A Brief History of a Confused Terminology. Front Neuroinform. 2018;11:76.

In Idaho, where they also have 65+ mph highways with traffic light intersections, they have the "stop light ahead" signs, but instead of having long yellow lights, there are lights on the "stop light ahead" sign. (The lights on the sign will start flashing several seconds before the traffic lights change to yellow.) The rule is basically the same though, if you pass the sign before its lights start flashing, you'll make it thru the intersection, otherwise, start slowing down.

> Code review during the peer review process

Unfortunately, this would make the already laborious process of peer review even longer and require more work. Given the reality of academia today (publish vs perish), not to mention the added work of preparing even well structured, version controlled code (which is not, in my experience common) for publishing, most researchers would not opt-in (or support) something which would make publishing more difficult.

> programmers on staff

That is generally referred to as "research software engineers/groups" and are unfortunately currently fairly rare in academia, but are becoming more common. RSECon is dedicated to this topic, and hosts a list of research software groups [1]

[1]: https://rse.ac.uk/community/research-software-groups-rsgs/

My perception is that CS is the only field which has generally normalized and accepted pre-prints in lieu of formally peer-reviewed articles. I can say that in my field (Health Sciences), biorXiv is the most applicable pre-print site, but in my experience, none of my colleagues have heard of it.

> This article is aimed at religious people.

I didn't get that at all. I think the author was trying to explain that the concept of the Sabbath (ie take a day of rest) has important psychological and societal value, irrespective of its religious origins.

> constant, gnawing sense that you might not be doing things good enough

While that is a very common feeling, Christianity at it's core, is supposed to be an admission of inadequacy. "As a human, there is nothing I can ever do that will be good enough."

> From a lawmaking perspective, it can be construed as "we looked at the issue, and found low-level employees to be worthy of protection, but nobody else."

I think a political perspective is probably more relevant/accurate which would likely be along the lines of "we looked at the issue, and protecting low-level employees is the most we could do and still get the bill passed"

Obviously large employers have vested interests in protecting non-competes and also have the lobbying budgets to successfully oppose the passage of stronger individual protection from non-competes

While Jupyter is not technically an IDE, I've found it a more than adequate replacement for the MATLAB environment. When I used MATLAB, I didn't often need to use the debugger, so the "IDE" that I actually use/need is mainly just an integrated REPL and code editor. Jupyter serves that purpose and also has the benefit of providing a very literate history of your research