Move Sampler execution spans page to be with Sampler

[jyu00]

URL to the relevant guide or resource

https://quantum.cloud.ibm.com/docs/en/guides/monitor-job#view-sampler-execution-spans

Select all that apply

• new content request
• typo
• code bug
• out-of-date content
• broken link
• other

Describe the fix or the content request.

We often get asked about execution order and timing, which is provided by Sampler execution spans. However, that information is buried in the Monitor or cancel jobs page, which is not an obvious place people would look for. Since we are splitting the primitives section by the type, we should move the execution spans info to be with Sampler, especially since Executor will also have its own page about batching and timing.

For new content requests - if the request is accepted, do you want to write the content?

I only want to review the material when it's finished

[abbycross]

@beckykd does this work fall in with the work you're currently doing, or should/can we do it separately?

[beckykd]

@jyu00 in #4640 , the Sampler input output page has a "view execution spans" section. But the Monitor jobs page still uses execution_span in some examples. Should I remove that code from Monitor jobs, or link from Monitor jobs to Sampler input output for more information?

[jyu00]

@jyu00 in #4640 , the Sampler input output page has a "view execution spans" section. But the Monitor jobs page still uses execution_span in some examples. Should I remove that code from Monitor jobs, or link from Monitor jobs to Sampler input output for more information?

Yeah it's an oversight from my review. The code block in this example also doesn't match the description. I can make a more detailed comment in 4640.

[jyu00]

I can make a more detailed comment in 4640.

Never mind, I mistakenly thought the changes came from 4640.

It's not entirely related to this issue (I can open a separate one if you prefer), but this section needs to be fixed:

1. Remove the backslashes in Call service.job(\<job\_id>)
2. The first paragraph talks about retrieving jobs, even though the section is titled "Retrieve job results"
3. All of these code blocks should be deleted, since they have nothing to do with "returns the 10 most recent runtime jobs that were run on my_backend". Only the last code block does that.

4. This example doesn't show getting job results.

[jyu00]

I also noticed we have an entire page on Retrieve and save job results, so it seems unnecessary to talk about Retrieve job results at a later time in the Monitor or cancel a job page?

[abbycross]

@jyu00 We have a draft PR intending to clean up the monitor/cancel job page, to format it like the View backend details page. It's on hold till all the restructuring work around the primitives is done. Is it better to integrate those changes here or can we add them to the other PR?

[jyu00]

@jyu00 We have a draft PR intending to clean up the monitor/cancel job page, to format it like the View backend details page. It's on hold till all the restructuring work around the primitives is done. Is it better to integrate those changes here or can we add them to the other PR?

The other PR is fine.

[abbycross]

Done