Hacker News Reader

Comment by byteknight | Hacker News Reader

What causes all of these papers published on github without code?

It is not unusual for code release to follow paper release with a lag of days to weeks. The top priority for a researcher is to get the paper out. Code is supporting material of secondary importance.

There is also Zero123++ which seems to be doing the same thing but has code available https://github.com/SUDO-AI-3D/zero123plus

EDIT: Just realized this one only outputs multiple images which are 3D consistent, not a 3d model.

I believe Zero123++ gives you the ability to generate consistent images from multiple camera views, where as DreamCraft3D seems to output 3D models with geometry and textures if I'm understanding it right. Like I could take the output of DreamCraft3D (if I had the code) and drop the result into Blender for example.

I was wondering why all of those papers have PDF downloads with the most useless, non-descriptive, names.

> Paper_high_res.pdf

Probably the same kind of oversight that just allowed me to compile hundreds of books in a catalog each as "book.pdf"

It was on exactly the second download where I realized how restrictive my choice of namespace was

The authors aren't thinking about you when they name the 87th revision of their paper.pdf They just want to get some sleep.

I used to give descriptive names to directories that would each carry a main document, and associated materials like references, diagrams, etc. Since the directory already had a descriptive name, I used to name the main document like "-- paper.docx" so that it stays on top when sorting the files by name.

However, realizing the problem you have mentioned, I started giving descriptive names to the main document also, in most cases by re-using the name given to the directory, still adding the leading "--".

Massive receptive AI audience.

The papers published on GitHub are typically presented in a much more accessible and beautiful way than arXiv.

The downstream social traction is further signal and affirmation for your results, lab, and/or company.

The fourth line of the readme

> Code will come soon.

Proof is in the pudding, so to speak.

Reply on news.ycombinator.com