Opened 9 years ago

Last modified 9 years ago

#234 assigned enhancement

experimentSolutionChannel has multiple solutions per channel

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

Description (last modified by dzollars)

Looking at the experimentSolutionChannel table we find that the channelID's are always 1. This is a handle into the optical systems tables, which aren't being used at all. So there are a couple of ways to proceed.

The first way is to start using these tables. I haven't thought through how all of this would work exactly, but the way I see it for each triple there would be a new opticalSystemSetting table entry that references an entry in one of those satellite tables. There would also be a new entry in the channel table, which would be a link into this group of tables from the experiment or the solution tables. To be true to form, we should remove runType from the experiment table, and start using these tables to determine the optical system when we want to know it. A major undertaking at this point.

A second way is to delete these tables. Perhaps we could migrate any settings we need into the channel / abstractChannel tables, and then treat them in much the same way as solutions or rotors. In other words, a button could be added in us_convert that would enable the user to select which channel is being used for each cell, or to create a new one based on an abstractChannel. Much more doable.

Any ideas?

Change History (1)

comment:1 Changed 9 years ago by dzollars

  • Description modified (diff)
  • Status changed from new to assigned
  • Type changed from defect to enhancement
Note: See TracTickets for help on using tickets.