Skip to content

Slightly update README file and spiff up formatting#768

Merged
mhucka merged 8 commits into
masterfrom
mh-update-readme
Jun 18, 2025
Merged

Slightly update README file and spiff up formatting#768
mhucka merged 8 commits into
masterfrom
mh-update-readme

Conversation

@mhucka
Copy link
Copy Markdown
Collaborator

@mhucka mhucka commented Jun 13, 2025

The way sections were arranged in the README file left lacked hierarchical consistency. In addition, there was not much of an introduction, which could leave new visitors a bit confused. I made the section structure more hierarchical, moved a section or two around for better logical flow, and added the usual badges and other visual elements at the top.

A formatted version of this updated README can be seen at https://github.com/quantumlib/qsim/blob/mh-update-readme/README.md

mhucka added 2 commits June 13, 2025 22:31
The way sections were arranged in the REAMDE file left lacked
hierarchical consistency. In addition, there was not much of an
introduction, which could leave new visitors a bit confused. I
made the section structure more hierarchical, moved a section or two
around for better logical flow, and added the usual badges and other
visual elements at the top.
@mhucka mhucka marked this pull request as ready for review June 13, 2025 22:34
@mhucka mhucka requested review from dstrain115 and pavoljuhas June 13, 2025 22:35
@mhucka mhucka force-pushed the mh-update-readme branch 2 times, most recently from f29c19e to d9db759 Compare June 16, 2025 04:36
@mhucka mhucka force-pushed the mh-update-readme branch from d9db759 to 5d4ba49 Compare June 16, 2025 04:44
Comment thread README.md Outdated

</div>

_qsim_ and _qsimh_ are Schrödinger and Schrödinger-Feynman state vector
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is qsimh still a thing? I thought that disappeared years ago. (maybe I am thinking of a different one though?).

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is qsimh still a thing? I thought that disappeared years ago. (maybe I am thinking of a different one though?).

Hmm. I will check.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update: qsimh is indeed no longer used. I've updated this PR to remove mention of qsimh from the README and will open a ticket to remind us to delete it from the rest of the distribution.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

C.f. #772

Comment thread README.md
### Input format

> [!WARNING]
> This format is deprecated, and no longer actively maintained.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we drop it from the docs if it is no longer maintained?

Copy link
Copy Markdown
Collaborator Author

@mhucka mhucka Jun 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we drop it from the docs if it is no longer maintained?

That would be better. I'll remove mention from the README; however, it's probably best to leave the description somewhere in the docs themselves, in case there's some (old) software that still uses it. I'll add the notes about deprecation wherever it's mentioned in the rest of the docs.

I need to also check if the builds & tests make use of this format and deal with those.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I take it back: there are examples in the docs that use the input format, and it would take time to figure out how to update things. In the interest of trying to get this release out, I'll open an issue instead, and deal with this for the next release (unless you have strong objections, @dstrain115).

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

C.f. #771

@mhucka mhucka force-pushed the mh-update-readme branch from a548e21 to 83b4011 Compare June 16, 2025 15:20
@mhucka mhucka mentioned this pull request Jun 16, 2025
@mhucka mhucka requested a review from sboixo June 16, 2025 17:39
@mhucka mhucka changed the title Adjust and spiff up README format Slightly update README file and spiff up formatting Jun 17, 2025
@mhucka mhucka enabled auto-merge (squash) June 18, 2025 21:43
I found it hard to scan the text in that intro due to the way that
the references were formatted. It seems good enough to put them
inline, so I did.
@mhucka mhucka disabled auto-merge June 18, 2025 23:17
@mhucka mhucka merged commit bcc6b11 into master Jun 18, 2025
48 checks passed
@mhucka mhucka deleted the mh-update-readme branch June 18, 2025 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants