https://t.co/LjpdlHa0C7 is getting a good face-lift.
Samples now have variant tables with annotation on their impact to the gene.
There is also an IGV integration. You need IGV installed locally but the Start|Jump links will open up you BAM file in IGV.

You must have IGV open and then click the start link.
The sample's BAM will show up for viewing in IGV.
Once open, you can use the jump link to move swiftly around to each variant. This is a variant in THCAS.
You can jump to other variants in the same gene. In this case we have one non-synonymous variant in phase with a synonymous variant in THCAS.
Cannabinoid synthase genes are cute but some folks can answer those questions with HPLC.
How about flowering genes?

This sample has a disruptive in frame deletion on a late flowering gene. And it's very rare in the population.
Looks to be heterozygous....
But its never this simple in cannabis.

Let's look at what other damaging variations it has.
7 Damaging inframe deletions or insertions (indels) in Early and Late flowering genes.
When it comes to Indels, IGV can be very helpful to inspect the read frequency and if there appears to be any read mismapping with short reads. They all look real and diploid.
Here is another one in AAE1-2. This gene is involved in making the pre-cursors to cannabinoid synthesis.

It is not just a simple presence or absence of the cannabinoid synthase genes. One has to pay close attention to variants up stream in the pathway as well.
@threadreaderapp unroll

More from Tech

After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.


This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.

We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.

Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.

This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile

You May Also Like