Ticket #448 (closed defect: invalid)

Opened 5 years ago

Last modified 5 years ago

Make sample generation a user-aware step

Reported by: business@… Owned by: work@…
Priority: major Milestone: 0.8.2
Component: Unknown Version: 0.8.1
Keywords: Cc:
Hardware: Operating system:
Product: URL:


Sample generation remains buggy sometimes. When I read the code it seems OK to me, but in practice I saw today once almost all samples disappear in a study while working in the wizard, and also sometimes samples that should be deleted are not. See video at http://screencast.com/t/rjxTZTSr for how to reproduce, and after you follow these steps and you click on e.g. 3. Events you also get the following errors:

parent → parent is required and may not be left blank

parent → parent is required and may not be left blank

parent → parent is required and may not be left blank

I think it would be more transparent to the user to include a 'Generate samples' step where the user actually request the (re-)generation of the samples. We could even supply some options. One important improvement would be to include not only the sampling event template name and sampling event start time, but also other sampling event fields such as Tissue and Organ if filled in. Will create a separate feature request for that if I get that request from more users.

Change History

comment:1 Changed 5 years ago by work@…

Also see ticket #443

I don't agree with you it should be a seperate step to generate samples, as the generation of the samples depends on subjects, event grouping, events, etcetera. The bussiness logic is now incorporated in the the actions performs inside your study. Moving this out is quite some refactoring work and prone to error

comment:2 Changed 5 years ago by work@…

about the screencast, was the whole event grouping table visible? Was subject 48 not checked somewhere on the right of the table (out of the visible area)?

comment:3 Changed 5 years ago by work@…

  • Status changed from new to closed
  • Resolution set to invalid

But I cannot do much with such a bug report...

Closing issue as invalid as it is lacking the steps to reproduce. Also I can't see the top overlay containing the revision number which may help as well...

Note: See TracTickets for help on using tickets.