Hi Unixchick,

We are hoping to share updates from these 3 teams in the coming weeks. We will share a research update from the ARP team soon. We are meeting with the OPN team this week so will hopefully have some news to share from them, too. The principal investigator from the HSTB team has been transitioning to a new research institution, which takes time, but they have said that they will send us an update soon. We understand the request for specific time frames, but we are only able to share information from each project as it is made available to us.

Thanks for your patience and understanding as we await updates from these teams.

Thank you so much TigerLily. You have already provided more info than I had. I look forward to whatever updates you have later.

These are for a new target (FLI1), and the receptor is quite a bit smaller than the MyoD1 targets; they seem to finish a lot quicker than those older tasks so I suspect we'll burn through these quite quickly :-)

So far, I've seen tasks from batches 4213 to 4220 and 4222 (where's 4221???). Adri's script seems to have picked up several of these already; it'll be interesting to monitor this...

Cheers - Al.

SCC1_0004222_FLI1-A_83969 2023-07-16 16:19:34 UTC

Even with older cpu's I'm am just ripping through these on Linux, with many 30 to 45 minutes with a few even under 30 minutes.

Cheers

You see, each hour, and as soon as a SCC1-task that has run on my systems has been validated, its batch number will be looked up and the date will be added if the batch is new or if some other 10% boundary (of its sequence in that batch) has been crossed.

(So, after a task called SCC1_0005000_Sig-D_0000_0 reaches my system, an entry for its (new) batch number 0005000 will be created and its 'sent by Server' date will be used as 'time reference' but only as soon as it has been validated.)

Note that my systems have loads and loads of tasks, so it takes time to process some and then to reach the beginning of a new batch or even a 'new' 10% boundary. I'm pretty certain people will understand that they'll need to have patience, and even if they don't, they will need even more patience. (There can't be enough patience in this matter. )

So, in the meantime, at the time of my writing this (it's 5 hours later now - should I offer my apologies for answering this late? ), the script has picked up on the current date, the 16th, and it has been adding batch 0004221, and spotted that batch 0004214 has been finalized and all other (currently) active batches have been promoted with some 10% boundaries today.

If you want to have a look at which latest SCC1-task my systems have received in the past hour, as part of a workunit, please take a look at this link - and remember, that task will be processed 'soon' i.e. with patience.

Adri