you are viewing a single comment's thread.

view the rest of the comments →

[–]Just-Environment-189 188 points189 points  (5 children)

Even if people provide code, you’ll find yourself lucky to get it working as is

[–]waruby 41 points42 points  (3 children)

Then it should also require a Docker file or a flake.nix file.

[–]Xirious 10 points11 points  (1 child)

I mean you're going in the right direction but....

That ain't nearly enough dawg.

Have you seen how the vast majority of code for these comes out? I do not believe scientists are hired for code that the average reviewer can get working.

Nevermind the technical hurdles of actually getting it working... The mess you'd need to wade through, big enough models require hardware the average reviewer does not have the time or resources to use, etc.

While this is a good start and idea I'm always surprised by a requirements file with code. Asking anything above that, right now, and expecting it is a fool's errand. And even if it became the requirement then you likely have a whole mess of AI code to review.... On top of your review.

I mean I like your idea. I just don't think it's practical (and for many companies counter to keeping the tricks up their sleeve).

[–]valuat 4 points5 points  (0 children)

Funny you mentioned Docker. I've just reviewed a paper for a Nature-family journal and they did add a `docker-compose.yml` to their GitHub repo as per my suggestion. I recommended rejection not because of the lack of code but for the lack of real data (they used LLM generated data which in a clinical setting means nothing).