Opened 9 years ago

Closed 9 years ago

#210 closed defect (fixed)

back-end update e-mail messages

Reported by: demeler Owned by: bdubbs
Priority: normal Milestone: future
Component: ultrascan3 Version:
Keywords: Cc:

Description

The e-mail message to the user that is sent when a job completes doesn't contain the name of the run and the triple that was analyzed. Also useful would be if the model contains ti or ri noise files. There is no way for the user to tell which run completed when they have submitted multiple.

Change History (6)

comment:1 Changed 9 years ago by bdubbs

  • Status changed from new to assigned

comment:2 follow-up: Changed 9 years ago by bdubbs

What do you want it to look like? The filenames of the results look like:

demo1_intensity-test10.2DSA.2e7a8fdc-a7cd-4791-b9ad-2ed934b92bfb.xml
demo1_intensity-test10.2DSA.4fed8586-da3d-46a7-a660-5913c8f761da.xml
demo1_intensity-test10.2DSA.541ff920-cba7-46b0-a6b2-bea47a7d945f.xml
demo1_intensity-test10.2DSA.74d8eca3-3768-4ca8-a185-3bab45608321.xml
demo1_intensity-test10.2DSA.9a9e8b43-7eb4-46f6-98ca-88b6dc7eda0e.xml
demo1_intensity-test10.2DSA.be3520ab-7e6f-4546-8748-204acf41966f.xml
demo1_intensity-test10.2DSA.d073348e-4093-41cd-9096-2cba1d5dfc8a.xml
demo1_intensity-test10.2DSA.ebae3c35-bf8e-4d3b-b560-d4b029d89335.xml
demo1_intensity-test10.2DSA.ed5555bd-a79d-47ac-b134-305e965e5432.xml
demo1_intensity-test10.2DSA.fbc58b93-3d22-4b9c-89a0-60ed429f340c.xml
ti.noise.3d4a614d-7604-49ff-8902-2e3ef67007d6.xml
ti.noise.45765ce3-e13b-4ad2-803b-63d3ae6b7221.xml
ti.noise.45d995f4-7fe8-41ae-87ba-86ceb0c44406.xml
ti.noise.7321a8b4-cba8-4b5a-8f53-a72e92651dbc.xml
ti.noise.8177f2d9-bdaf-42d6-9943-6420d1aac31d.xml
ti.noise.86d2504b-1207-4989-a3c5-ce65a4650ac8.xml
ti.noise.9b913de4-b20e-48b8-8fab-41371f62fa11.xml
ti.noise.9dd42a1d-ff83-4ac4-abf5-6b18fd11b79d.xml
ti.noise.b4c579de-de2f-40e2-90b2-f816325b00fd.xml
ti.noise.cca815c9-ce71-4520-9f45-6a9956f95d0d.xml

The first are model files and the noise files are obvious. The guid values are unique for each model and noise calculation.

For the simple case, I can look up the edited data ID from the model guid and get the triple from the edited data filename.

What information to display for a global fit is more complicated. In the results, I only have the editID of the 1st dataset.

Reporting information from the back end to the analysis viewer is easy. Everything is already parsed.

Depending on what you want, this ticket can result in major changes to the results handler and possibly require changes to the back end itself. Any changes need to be able to handle all valid combinations of 2dsa, ga, mc, noise, meniscus fit

comment:3 in reply to: ↑ 2 Changed 9 years ago by demeler

Replying to bdubbs:

What do you want it to look like?
Depending on what you want, this ticket can result in major changes to the results handler and possibly require changes to the back end itself. Any changes need to be able to handle all valid combinations of 2dsa, ga, mc, noise, meniscus fit

So this is not so important for the workshop, which is why I labeled it for the future. But for the user it would be helpful to find out:

  1. what run (or runs) was it (i.e., demo1_intensity-test10)
  2. what triple (or triples) was it
  3. what analysis method was it (2DSA, GA, 2DSA-MC, 2DSA-MW, etc)
  4. was a meniscus fit performed
  5. are noise files included
  6. If it was a MC run, how many iterations

Keep in mind that we should prevent certain combinations anyway since they don't make sense, for example, MC or global analysis at the same time you do noise fits or meniscus fits, so you wouldn't have to worry about them. If it is easy to add at least the run ID and the triple, this would be my most important change, the rest could be done later, or everything about this ticket could be postponed if other things are more pressing.

comment:4 follow-up: Changed 9 years ago by bdubbs

With some recent changes, I am able to extract the triple and other info. The mail message now looks like this:

   Your UltraScan job is complete:

   Submission Time:  2011-05-25 16:20:02
   Analysis ID    :  5890.alamo.biochemistry.uthscsa.edu
   Status         :  completed
   GFAC Status    :  COMPLETE
   Cluster        :  alamo
   Job Type       :  2DSA

   model triple 6/B/230; meniscus: 6.077; variance: 9.98827e-06;
   model GUID d0f49fd3-8168-4110-ac61-f6012c0ac35c
   noise triple 6/B/230; noise GUID 016e129b-0329-49a8-bf52-c84612592c16

If there are multiple meniscus runs or monte carlo iterations, there will be additional lines order computed.

Is this sufficient or do you want additional information?

Note that this probably only works on alamo right now. The other clusters need an update to make the info available to the mail code.

comment:5 in reply to: ↑ 4 Changed 9 years ago by demeler

Replying to bdubbs:

Is this sufficient or do you want additional information?

I would say it is sufficient for the e-mail message. We still need some way to get the meniscus positions and associated rmsd values from the back end into a format that can be understood by us_fit_meniscus.

comment:6 Changed 9 years ago by bdubbs

  • Resolution set to fixed
  • Status changed from assigned to closed

Getting the meniscus info to us_fit_meniscus is #213.

Note: See TracTickets for help on using tickets.