DO NOT LOOK AT THE SOURCE CODE DO NOT LOOK AT THE SOURCE CODE DO NOT LOOK AT THE SOURCE CODE
i may never recover
29.01.2026 14:13
👍 2
🔁 0
💬 1
📌 1
DO NOT LOOK AT THE SOURCE CODE DO NOT LOOK AT THE SOURCE CODE DO NOT LOOK AT THE SOURCE CODE
i may never recover
Tough to say without more details, but: provide an argument or an R option that allows users to enable the new behavior, but default to the old style while returning a warning that the old behavior will be deprecated in a later version. Later, alter the default before removing the old one.
Pick a time, I'll be there!
You can pry emacs from my cold dead fingers.
That being said, if you're not using this, you're missing out: github.com/kahole/edama...
If any #rstats folks use `cloudyr/aws.s3`, a recent change in the S3 API may cause some weird issues. Over the coming days. A fix can be found here: github.com/cloudyr/aws....
A screenshot of R code solutions to Part 1 and Part 2 of the Advent of code puzzle. There are way too many regular expressions.
I love eval(parse()) crimes.
I set the additional challenge that I wanted it to be a single string that got eval'd & only using base regex methods.
I was just messing with this. No code written, but my plan was:
`uv export --format requirements-txt`, sed away the versions, then `uv add -r requirements.txt`.
But have you considered the career advantages of discovering a new -ome that only you uniquely have the magic touch to investigate
You close emacs?
Funny enough, this exists here: bsky.app/profile/xblo...
If I'm paying for software, I want the method to be great, yes, but what we really *want* to be buying is stability and maintenance so we can focus on our core products.
It was really disappointing. Ultimately came down to: inflexible legal / payment agreements (in one case wanting a several year commitment & full payment up front), and there's no guarantee the project won't die anyway due to funding lapses, etc. in which case we lose access, so becomes too risky.
Been on the purchasing side a time or two and we just decided to give up rather than deal with the headache.
Could also run something like mFOLD but I'm not fully convinced that translates to efficacy, but at the very least might indicate which ones are easier/harder to clone.
At that point I'd dip into genetic variants. More consistent seq across population == better? Avoid runs of same nt, prefer terminal GC clamp (or other platform-specific discriminators)?
I usually make a matrix of these scores & minimize (can weight or not)
No clue about the alt-nt pairing algo.
If the list is small, order em all?
(Where k is the length of your construct)
For ASOs I'm not as sure (other considerations there for alt-nt's for stability, etc), but for RNAi, it can be hard to predict what works best. If you have a fusion or something you can try spanning the boundary.
I like to grab all kmers in ROI & subset to unique ones vs the masked genome.
We are now well beyond my realm of expertise!
I guess it depends most on your delivery vehicle. Nusinersen works so well (in part) cause you can just inject directly into the spine. Not sure your cancer type of interest, but I think that is key here if the end goal is 'quickest to patient'. If you have to go through the liver, 🤷♀️
Ok but Fiesta Grill is at least an 11/10, I'd hardly call that low standards.
Are you more interested in knockdown, or specifically using ASOs to do the knockdown? Admittedly not familiar with implementing ASOs in the lab, but shRNAs are pretty easy to design & test a lot of.