Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server: interface to Zocalo #4

Open
d-j-hatton opened this issue Jan 25, 2022 · 5 comments
Open

Server: interface to Zocalo #4

d-j-hatton opened this issue Jan 25, 2022 · 5 comments
Labels
server Relates to the server component

Comments

@d-j-hatton
Copy link
Contributor

Mechanism for triggering analysis on a data collection. How will the various processing options be dealt with?

@d-j-hatton d-j-hatton added the server Relates to the server component label Jan 25, 2022
@HorstmannA
Copy link
Contributor

@d-j-hatton @Anthchirp I'm happy to look into this one but I'll need a bit of help. eg.

  1. What information do we need to send in order to trigger processing?
  2. Where does the information need to go?

@d-j-hatton
Copy link
Contributor Author

I think, as things currently stand, for the processing to be triggered you need an ISPyB processingJobId (pid) with a corresponding entry that has been setup correctly and then send a message to the processing_recipe queue with a message that looks like {"parameters": {"ispyb_process": pid}}

@HorstmannA
Copy link
Contributor

Thanks Dan, so once a Data Collection has been registered we can look up the pid and send the message to trigger processing?

@d-j-hatton
Copy link
Contributor Author

Yes, it will need both DataCollection and ProcessingJob entries

@Anthchirp
Copy link
Contributor

Code to achieve all of the above can be lifted from ispyb.job and zocalo.go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
server Relates to the server component
Projects
None yet
Development

No branches or pull requests

3 participants