Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

State visualizer sample readme is outdated #426

Open
tcNickolas opened this issue Sep 17, 2020 · 1 comment
Open

State visualizer sample readme is outdated #426

tcNickolas opened this issue Sep 17, 2020 · 1 comment

Comments

@tcNickolas
Copy link
Member

Describe the bug
The readme at https://github.com/microsoft/Quantum/tree/main/samples/runtime/state-visualizer looks out of sync with the code. The instructions suggest to edit Program.qs file, looking for QsMain operation, and neither exist. (Instead, the visualizer picks up whichever Q# operation is called from Program.cs, and in the sample this operation is from a different sample, rather than contained in this one.)

It would also be convenient to clarify that commands npm install and npm run release should be executed from the sample directory (I started by running them from elsewhere and got a bunch of confusing errors), and to specify whether they are part of one-time install or per-project setup.

@msoeken msoeken added good first issue Hacktoberfest Good issue for Hacktoberfest 2021 participants! labels Oct 6, 2020
@aishwarya-jhanwar-14
Copy link

  • On trying to modify the Program.cs file on line "visualizer.Run(SimpleGrover.SearchForMarkedInput.Run, 4L).Wait();" and adding our own program with the namespace name it is showing error as "'StateVisualizer' is a namespace but is used like a type." for line "var visualizer = new StateVisualizer(new QuantumSimulator());" .

  • It is also showing dependency issues if run along with new program like AspNetCore, DependencyInjection, Hosting, IWebHost, IHubContext does not exist and Startup, IClientProxy, StateVisualizerHub could not be found

Please help to fix this

@guenp guenp removed the Hacktoberfest Good issue for Hacktoberfest 2021 participants! label Dec 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants