Closed mikaell closed 4 months ago
I vote for squashing the default view.
I'd say squashing is a good option, regardless of how our three-body problem decomposes? Did you read the SF book by the way, or are you referring to the original physics issue? 😸
Rewrite to js lacks immediacy, and can always be done later without interfering with anything else, as long as the track data is anyway passed to Scout, so leave that one off for now.
Merge is still somewhat tempting to me, but it may be slightly slower to implement, is indeed somewhat more rigid as well as a little less immediate in conveying information to the user.
With regards to #71 we need to skynda långsamt whatever solution is chosen
Did you read the SF book by the way, or are you referring to the original physics issue? 😸
Both I suppose. Haven't got around reading the book yet. I limit myself to one thick book per year.
Type | Old Tags | Suggested New Tags |
---|---|---|
upd (regions) | ACC5322A2, chromograph | ACC5322A2, chromograph, upd, regions |
upd (site) | ACC5322A2, chromograph | ACC5322A2, chromograph, upd, sites |
Tcov | ACC5322A2, chromograph | ACC5322A2, chromograph, tcov |
-replace ACC5322A2 with sample_id.
Do we need a chromosome tag as well or are you planning to get that from the filename later?
Do we need a chromosome tag as well or are you planning to get that from the filename later?
Ideograms will be placed in public/static and committed into Scout.
Ideograms will be placed in public/static and committed into Scout.
Right! Then, I'll drop MIP's functionality to generate ideograms
Stale
Handling Hundreds of Files in Housekeeper
ping @dnil, @moonso, @henrikstranneheim, @jemten, @patrikgrenfeldt
The Three-body problem
Chromograph integration is stuck in the intersection of CG, Housekeeper and Scout. The reason is not knowing how the many (hundreds?) picture files should be handled and also to generate a configuration file pointing to the correct files. This is an invitation for discussion. Here are suggested solutions to the problem.
An ideal solution should:
Tar-ball (current)
The current solution is to create a tar-ball and hand it to Housekeeper. This solution is not working at the moment. Problems arise when unpacking it is implossible to know the filenames and therefore generate a configuration to Scout.
A solution is to guess filesnames with hearuistics and a strict naming convention.
(+)
(-) Who handles the tracking and deleting of the unpacked files? Not working at the moment
Do Nothing
Add hundreds of picture files as is into existing software.
(+) No implementation Conceptually true to Housekeeper
(-) The view from
housekeeper get
will be bloatedSquash Housekeepers View
Tweak Housekeeper's default view by squashing series of filenames -example below. Verbose flag would show everything.
(+) Conceptually true to Housekeeper Housekeepers view is not bloated Small implementation
(-)
Add Directory Handling in Housekeeper
Add functionality to Housekeeper to add and handle directories (adding dirs is already possible, but not delete them).
(+) Small implementation Housekeepers view is not bloated
(-) Changes Housekeeper concept Have not thought through semantics of this change
Merge PNGs Into One
Instead of handling hundreds of picture files, merge them into one.
(+) Housekeepers view is not bloated
(-) Loose granularity and flexibility Not future proof for adding functionality
Rewrite Chromograph in Javascript
Rewrite picture generation to be done in Scout just in time.
(+) ?
(-) Unknown implementation time Unknown problems
Other solutions are welcome! Preferably this can be decided quickly.