You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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
andnpm 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.The text was updated successfully, but these errors were encountered: