The pre CISION tech is simply an attempt to improve the safety profile... 2/10
AVA6000 approved by MHRA. Superb news. First dosing 'around mid-year'; first data to come within 3-4 months after that.
A summary thread on the significance of AVA6000 - and #AVCT's pre CISION platform as a whole - to both the oncology industry and to AVCT itself. 1/10
The pre CISION tech is simply an attempt to improve the safety profile... 2/10
Most therapeutics going through clinical trials look for an improvement of at least 20% over the existing industry-standard drug. A 50% increase in efficacy would usually be considered an astonishing result.
In pre-clinical mouse models for #AVCT's AVA6000 3/10
What this means is that the pre CISION tech could be used to enable the giving of doses to patients that are multiple times more potent... 4/10
For example, in #AVCT's pre-clinical trials, pro-dox (AVA6000) doses were 6x more potent than the standard dox doses.
The results? The...5/10
#AVCT isn't looking to improve chemotherapies by 25-30%, like most drugs in clinical trials.
Its pre CISION has the potential to improve the safety profile - and thus the... 6/10
https://t.co/XOEE45CBtZ
AVCT holds the global exclusive licence over...8/10
TMAC will produce Affimer Drug Conjugates - a potentially more powerful class of oncology treatment than Antibody Drug Conjugates. 9/10
First though, success for AVA6000 please!
Then hopefully @avacta's first TMAC drug to enter Phase I next year 10/10
More from Society
Sandbank Danger, A Thread
Controversy Has Been Caused By The Digging Of A Narrow Channel By A Resort On A Sandbank Near K. Hinmafushi.
Hinmafushi Council President Shan Ibrahim Stated To Sun That The Resort, Which Dug The Trench Creating A River On The Sandbank, Did Not Have Ownership Over The Sandbank.
Officials From The Island Of Hinmafushi Had Traveled To The Sandbank To Stop The Process Of Digging The Trench When They Became Aware Of It, Said Shan.
Officials Were Now Redepositing The Sand Removed From The Sandbank.
Controversy Has Been Caused By The Digging Of A Narrow Channel By A Resort On A Sandbank Near K. Hinmafushi.
Hinmafushi Council President Shan Ibrahim Stated To Sun That The Resort, Which Dug The Trench Creating A River On The Sandbank, Did Not Have Ownership Over The Sandbank.
Officials From The Island Of Hinmafushi Had Traveled To The Sandbank To Stop The Process Of Digging The Trench When They Became Aware Of It, Said Shan.
Officials Were Now Redepositing The Sand Removed From The Sandbank.
— Ahmed Aznil (@AhmedAznil) January 21, 2021
Krugman is, of course, right about this. BUT, note that universities can do a lot to revitalize declining and rural regions.
See this thing that @lymanstoneky wrote:
And see this thing that I wrote:
And see this book that @JamesFallows wrote:
And see this other thing that I wrote:
One thing I've been noticing about responses to today's column is that many people still don't get how strong the forces behind regional divergence are, and how hard to reverse 1/ https://t.co/Ft2aH1NcQt
— Paul Krugman (@paulkrugman) November 20, 2018
See this thing that @lymanstoneky wrote:
And see this thing that I wrote:
And see this book that @JamesFallows wrote:
And see this other thing that I wrote:
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.