<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Roivant Technology - Medium]]></title>
        <description><![CDATA[Learn about Roivant’s technology efforts, products, programs, and more. - Medium]]></description>
        <link>https://medium.com/roivant-technology?source=rss----dce2753b22fb---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Roivant Technology - Medium</title>
            <link>https://medium.com/roivant-technology?source=rss----dce2753b22fb---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:53:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/roivant-technology" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Faster API development with django-dataclasses]]></title>
            <link>https://medium.com/roivant-technology/faster-api-development-with-django-dataclasses-5d33c366f23c?source=rss----dce2753b22fb---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d33c366f23c</guid>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[django]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Alec Clowes]]></dc:creator>
            <pubDate>Tue, 11 Jan 2022 19:13:02 GMT</pubDate>
            <atom:updated>2022-01-11T19:13:02.101Z</atom:updated>
            <content:encoded><![CDATA[<p>Our new <a href="https://pypi.org/project/django-dataclasses/">django-dataclasses</a> library allows you to:</p><ul><li>Define your API schema using Python dataclasses</li><li>Use the dataclasses as request and response bodies in Django views</li><li>Generate a JavaScript API client from an OpenAPI export</li></ul><p>Why did we build this if there are many great libraries for building APIs in Python already?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*PRejZ_mkyqu9sPMNzLCTsg.jpeg" /><figcaption>Sniffing out a new development paradigm. Painting by <a href="https://archive.org/stream/cu31924001182181/#page/n502/mode/1up">G. Stubbs</a>, 1802.</figcaption></figure><h3>Why not…</h3><h4><strong>Use FastAPI?</strong></h4><p>I like the <a href="https://docs.djangoproject.com/en/4.0/topics/db/models/">Django ORM</a> and the overall quality of the Django documentation. <a href="https://fastapi.tiangolo.com/">FastAPI</a> does not recommend a particular ORM, but I think it is often used with SQLAlchemy which in my opinion is more complicated to use, has less usable documentation, and requires the use of a separate tool (<a href="https://alembic.sqlalchemy.org/en/latest/">Alembic</a>) to manage database migrations.</p><h4><strong>Use pydantic?</strong></h4><p><a href="https://pydantic-docs.helpmanual.io/">pydantic</a> does almost exactly the same thing as dataclasses-jsonschema, and when used with FastAPI it is a similar solution to Django + django-dataclasses. However, pydantic does not do schema validation; if you pass it a float it will silently converted to an integer as <a href="https://pydantic-docs.helpmanual.io/usage/models/#data-conversion">documented here</a>.</p><h4><strong>Use Django REST framework?</strong></h4><p><a href="https://www.django-rest-framework.org/">Django REST framework</a> (DRF) is powerful but complicated if you use the the class-based views and override methods like <em>get_object</em> or <em>filter_query</em>. The REST paradigm adds complexity such as serializers which accept different fields on GET versus POST.</p><h4><strong>Use gRPC?</strong></h4><p>I prefer <a href="https://grpc.io/">gRPC</a> for API development and I have used it with the Django ORM, but some projects require JSON serialization. The HTTP/2 streaming features, compact protobuf serialization, and code generation features are great if you don’t need JSON.</p><h3>What it is</h3><p>django-dataclasses glues together the <a href="https://github.com/s-knibbs/dataclasses-jsonschema">dataclasses-jsonschema</a> library and Django, allowing you to use Python <a href="https://docs.python.org/3.8/library/dataclasses.html">dataclasses</a> to define the request and response schemas for a Django view. An example illustrates this best:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c545a2c7b1ac773f94566d90f380682/href">https://medium.com/media/3c545a2c7b1ac773f94566d90f380682/href</a></iframe><p>Most of the value enabled by django-dataclasses is implemented by the dataclass-jsonschema library, so kudos to <a href="https://github.com/s-knibbs">Simon Knibbs</a> for his work in that package.</p><p>The type annotations on the view function tell the django-dataclasses wrapper which schemas to use for the request and response.</p><h3>The simplicity of procedure calls</h3><p>The RPC (Remote Procedure Call) paradigm is based on actions as opposed to the object state used in REST (REpresentational State Transfer). The RPC approach is valuable it encourages developers to make API methods that do one thing well, whereas REST encourages all actions on an object to be grouped into a single method. For example, a hypothetical REST endpoint for a user object like /user/1 could support changing the username or the password, and the developer may expect API clients to do one or the other but not both. A bug of this type could be an issue with either approach, but RPC encourages these actions to be implemented as two separate methods.</p><p>RPC is also better suited to payloads which contain information about multiple related objects because there is no presumption that the payload represents a single object type. A strict REST approach would require decomposing this into separate endpoints, which is inefficient. Similarly, REST objects are often one-to-one with database models, which makes changing either difficult. RPC has no opinion on the contents of the payload, thereby encourages endpoints tailored to a specific client need and not mapped directly to a single database model. <a href="https://graphql.org/">GraphQL</a> is based on a similar learning, but does not try anticipate the client’s needs at all!</p><h3>Sharing the API definition</h3><p>Having written the API, why should clients redefine the request and response schemas and associated URLs? django-dataclasses provides an export of your schemas in the OpenAPI format using a management command:</p><pre>./manage.py openapi_export &gt; api.json</pre><p>The export can be passed to a tool like <a href="https://github.com/ferdikoomen/openapi-typescript-codegen">openapi-typescript-codegen</a> to generate a JavaScript client library that provides the TypeScript types and methods for calling the API:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1340013b4e2b49200c7147d41cd7dd18/href">https://medium.com/media/1340013b4e2b49200c7147d41cd7dd18/href</a></iframe><p>To use the client in your code, you write something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e16128da42b38a9628e365b85813109/href">https://medium.com/media/7e16128da42b38a9628e365b85813109/href</a></iframe><h3>Conclusion</h3><p>API development is constantly improving as new tools remove boilerplate code and support better type checking. I hope you find the django-dataclasses library useful, and contribute by sharing issues or creating merge requests. Thanks!</p><ul><li><a href="https://pypi.org/project/django-dataclasses/">https://pypi.org/project/django-dataclasses/</a></li><li><a href="https://gitlab.com/roivant/oss/django-dataclasses">https://gitlab.com/roivant/oss/django-dataclasses</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d33c366f23c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/roivant-technology/faster-api-development-with-django-dataclasses-5d33c366f23c">Faster API development with django-dataclasses</a> was originally published in <a href="https://medium.com/roivant-technology">Roivant Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Complex Twitter Search Queries]]></title>
            <link>https://medium.com/roivant-technology/managing-complex-twitter-search-queries-21bc5d2645c3?source=rss----dce2753b22fb---4</link>
            <guid isPermaLink="false">https://medium.com/p/21bc5d2645c3</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[google-cloud]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[twitter-data]]></category>
            <dc:creator><![CDATA[Andrew Lange]]></dc:creator>
            <pubDate>Tue, 02 Nov 2021 14:31:31 GMT</pubDate>
            <atom:updated>2021-11-02T19:58:06.674Z</atom:updated>
            <content:encoded><![CDATA[<p>Our approach to managing complex Twitter search queries using Python and BigQuery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*1zpDz8u3c1L9oC4h.jpeg" /><figcaption>A data scientist after successfully analyzing Twitter data without needing to spend hours munging.</figcaption></figure><h3>The Problem</h3><p><strong>Twitter</strong> is currently the go-to source to find out what’s happening — products, people, politics — it’s all there. Originally unveiled as a social media platform, it has become the world’s data feed — a place where all global events are logged synchronously.</p><p>For a scientist at Roivant Discovery, these data offer a trove of potential cutting-edge research and insight. To unlock this potential, <strong>scientists need a way of collecting Twitter data</strong> on a reoccurring basis <em>without</em> spending an inordinate amount of time querying and munging.</p><p>As data engineers at Roivant Technology, we were tasked with figuring out:</p><ol><li>How will our users build <strong>filters</strong>?</li><li>How do we <strong>collect</strong> and <strong>store</strong> the results of these filters?</li></ol><h3>Our Approach</h3><h4>Building Filters</h4><p>There are <strong>two approaches</strong> to filtering Twitter data (via API v1 standard):</p><ul><li><strong>Stream </strong>— Tweets arrive as soon as they’re published</li><li><strong>Search </strong>— Tweets arrive as results to a query</li></ul><p><strong>Streaming</strong> is an appealing option due to its low latency. But streams are high maintenance — when one goes down, any missed records must be filled in. Another pitfall: each Tweet only flows through a stream <em>once</em>. This makes it difficult to analyze a Tweet’s performance over time.</p><p>The real deal-breaker is that the streaming filter is <em>only</em> capable of using basic stream parameters (e.g. follow, track, location) which are insufficient for the complex filters required by our users.</p><p>We decided to pursue<strong> Search </strong>because it provides the ability to filter Tweets using search query operators. For example, we can isolate NYC subway delays specifically on the 4/5 line:</p><pre>from:NYCTSubway (delay OR delays OR stopped) &quot;4/5&quot;</pre><p>We considered allowing users to maintain a list of their own custom search queries. However, we realized that would become a nightmare 😅:</p><ul><li>Prone to human error, leads to invalid queries</li><li>Tedious, waste of time</li><li>Difficult to make incremental updates over time, no lineage</li></ul><p>We decided to <strong>create a layer of abstraction</strong> over search_query<strong> </strong>called a report. Each report object contains a criteria array in which each item represents a clause in a search_query:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9a1a23334c944705edabad3ef955bdfc/href">https://medium.com/media/9a1a23334c944705edabad3ef955bdfc/href</a></iframe><h4>Collecting and Storing Results</h4><p>To <strong>collect</strong> the results of a search query, we used tweepy instead of hitting the Twitter API directly. This is because tweepy is well-supported and solves a number of <strong>challenges</strong> out-the-box:</p><ul><li>Rate-limitation</li><li>Pagination</li><li>Authentication</li></ul><p>For <strong>storage</strong>, we elected to use <strong>BigQuery</strong> as we expect our tables to grow (&gt;100GB). We created a <strong>table</strong> to persist <em>all</em> Tweets (to analyze engagement over time), and a <strong>view</strong> to provide the <em>latest</em> version of each:</p><pre># `status` table<br>id,inserted_at,created_at,status,likes,favorites<br>123,2021-01-15 02:30,2021-01-14 23:05,This is a Tweet!,15,25<br>123,2021-01-16 02:33,2021-01-14 23:05,This is a Tweet!,64,32<br>123,2021-01-17 02:38,2021-01-14 23:05,This is a Tweet!,93,45</pre><pre># `status_latest` view<br>id,inserted_at,created_at,status,likes,favorites<br>123,2021-01-17 02:38,2021-01-14 23:05,This is a Tweet!,93,45</pre><p>This approach yields <strong>duplicate records.</strong> To keep storage costs down, we delete any extraneous records older than 7 days.</p><p>To this end, we wrote a twitter DAG comprised of the following <strong>tasks</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*gizo0ob0GCwXCqmBf8enRg.png" /></figure><h4>Orchestration</h4><p>We considered deploying our DAG to a Google Cloud Function. However, we<strong> decided to use </strong>dag-workflows so we can develop and run our code locally.</p><p>The dag-workflows Python library was built in-house to provide a means of writing and executing DAGs. Each DAG may be comprised of Python and/or SQL tasks that run <strong>on-demand</strong> or on a <strong>schedule</strong>.</p><p>At Roivant, each project has a dedicated dag-workflows scheduler deployed to a Kubernetes cluster on GKE. When it’s time for a DAG to run, a container is provisioned and the code is executed on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*iLK7eIeQ9blphbhaLzNGvQ.png" /><figcaption>Twitter DAG written using dag-workflows.</figcaption></figure><h3>The Solution</h3><ol><li>To <strong>build a filter</strong>, a POST request is sent to the create_report/ endpoint:</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/19f313a397ce66c48edb91c8710e8a80/href">https://medium.com/media/19f313a397ce66c48edb91c8710e8a80/href</a></iframe><p>A 200 signal indicates the report was successfully created and can be retrieved:</p><pre>SELECT * <br>FROM   report_latest <br>WHERE  report_slug = &#39;subway-delays&#39;;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*Mik4S89aAvK9P4JnBvyY4A.png" /></figure><p>2. To <strong>collect results</strong> of a report, the twitter DAG must be run. A user can wait until the next scheduled run (i.e. nightly), or trigger a run manually:</p><pre>kubectl exec -it -n &lt;NAMESPACE&gt; &lt;POD-HASH&gt; \<br>  -- /secrets-init/bin/secrets-init \<br>  --provider=google workflows dags.config trigger twitter</pre><p>During the DAG run, a new load_history object is created indicating the subway-delays report successfully returned <strong>10 Tweets</strong>:</p><pre>SELECT * <br>FROM   load_history<br>WHERE  report_slug = &#39;subway-delays&#39;;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NFy5R4KSxTdtW20WI-z6A.png" /></figure><p>3. To <strong>access results</strong> (i.e. these 10 Tweets), we query the status_latest view:</p><pre>SELECT status_created_at, <br>       status_id, <br>       user_screen_name, <br>       report_slug, <br>       load_uuid, <br>       status_text <br>FROM   status_latest<br>WHERE  load_uuid = &#39;04237096-131f-4c40-821d-ba3c6d0d4f9e&#39;;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JXnHYG1hqD_IAMcA50y-IQ.png" /></figure><p>Now a user can sit back and <strong>let the results pile up</strong> 🚀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GyDFNiuqbyvApRQ2RnBOIA.png" /></figure><h3>Useful Queries</h3><p>Our data model supports a number of <strong>useful queries</strong>. To demonstrate them, we’ll start by declaring a start_date and end_date:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/584c86fecf67a2e64e0d529ba435feac/href">https://medium.com/media/584c86fecf67a2e64e0d529ba435feac/href</a></iframe><h4>Reports by Engagement</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cbab694d38fc26e63776371eab4be80c/href">https://medium.com/media/cbab694d38fc26e63776371eab4be80c/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*AKE6g0IuLny-1sAqUVjQvw.png" /></figure><h4>Top Hashtags by Frequency</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/58ad8f4ef4ee6552baa00d2dbc841a14/href">https://medium.com/media/58ad8f4ef4ee6552baa00d2dbc841a14/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/176/1*0CobYB1ODMljtCZpnnTsMw.png" /></figure><h4>Top User Mentions by Frequency</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a100652d8693c07e900e283606d617dc/href">https://medium.com/media/a100652d8693c07e900e283606d617dc/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/226/1*C4TwS8Nj8pX-vFYslWgcUA.png" /></figure><h3>Call to Action</h3><p>Try collecting Tweets on your own using dag-workflows and BigQuery!</p><p>To help get you started, we’ve included a <a href="https://gitlab.com/roivant/oss/twitter-search-query">code sample</a> demonstrating the <strong>core functions</strong> used in <em>our</em> twitter DAG.</p><ul><li><strong><em>Code sample</em></strong>: <a href="https://gitlab.com/roivant/oss/twitter-search-query">https://gitlab.com/roivant/oss/twitter-search-query</a></li><li><strong><em>Sample DAG</em></strong>: <a href="https://gitlab.com/roivant/oss/workflows/-/tree/main/example_project/dags/trader_bot">https://gitlab.com/roivant/oss/workflows/-/tree/main/example_project/dags/trader_bot</a></li></ul><h3>Learn More</h3><p>We appreciate you taking the time to read about our data engineering challenges! Below you’ll find <strong>useful resources </strong>previously mentioned:</p><ul><li>Read: <a href="https://medium.com/roivant-technology/building-dag-workflows-16d5c40f7789">Building dag-workflows: a Python Workflow Execution Tool</a></li><li>Documentation: <a href="https://dag-workflows.readthedocs.io/en/latest/index.html">dag-workflows</a></li><li>Documentation: <a href="https://docs.tweepy.org/en/stable/">tweepy</a></li><li>Read: <a href="https://developer.twitter.com/en/docs/twitter-api/v1/tweets/search/overview">Twitter Search API</a></li><li>Read: <a href="https://developer.twitter.com/en/docs/twitter-api/v1/tweets/search/guides/standard-operators">Twitter Search Operators</a></li><li>Read: <a href="https://cloud.google.com/bigquery/docs/introduction">What is BigQuery?</a></li><li>Read: <a href="https://cloud.google.com/bigquery/streaming-data-into-bigquery#streaminginsertexamples">Streaming Data into BigQuery</a></li><li>Read: <a href="https://cloud.google.com/bigquery/streaming-data-into-bigquery#manually_removing_duplicates">Removing Duplicates in BigQuery</a></li><li>Read <a href="https://medium.com/roivant-technology/introducing-the-roivant-technology-blog-201972bbe49f">Introducing the Roivant Technology Blog</a></li><li>Work with us! View our <a href="https://www.roivantcareers.com/job/senior-software-engineer-vant-technology-technology-us-ny-new-york-151-west-42nd-s-4-1746959/">open positions</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21bc5d2645c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/roivant-technology/managing-complex-twitter-search-queries-21bc5d2645c3">Managing Complex Twitter Search Queries</a> was originally published in <a href="https://medium.com/roivant-technology">Roivant Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using AlphaFold2 to Predict the Structure of a Protein-Protein Complex]]></title>
            <link>https://medium.com/roivant-technology/using-alphafold2-to-predict-the-structure-of-a-protein-protein-complex-5d4dabe64cc5?source=rss----dce2753b22fb---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d4dabe64cc5</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[gpu]]></category>
            <category><![CDATA[pharmaceutical]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[simulation]]></category>
            <dc:creator><![CDATA[Huafeng Xu]]></dc:creator>
            <pubDate>Sun, 19 Sep 2021 02:56:33 GMT</pubDate>
            <atom:updated>2021-09-19T03:28:11.590Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://discovery.roivant.com/">Roivant Discovery</a> we have built a computational platform based on quantum physics to simulate the dynamic behavior of biomolecules (such as proteins and protein-protein complexes), to reveal the relationship between their dynamics and their biological activities, and to rationally design small molecule drugs that modulate their dynamic behavior to achieve desired therapeutic effects.</p><p>Our simulations invariably start from a 3-dimensional protein structure, or the protein-protein complex, of interest. The standard methods for deriving such structures are X-ray crystallography and more recently cryogenic electron microscopy (cryo-EM). We have routinely used existing structures in the public repository, <a href="https://www.rcsb.org/">Protein Data Bank</a> (PDB), and obtained our own structures by in-house crystallography. More recently, we have explored the use of <a href="https://alphafold.ebi.ac.uk/">structural models predicted</a> by DeepMind’s <a href="https://github.com/deepmind/alphafold">AlphaFold2</a>, which has demonstrated unprecedented accuracy in predicting the crystal structures of proteins, often approaching the experimental resolution of crystallography. We have been experimenting with the AlphaFold2 predictions and exploring how to integrate them into our drug design process.</p><p>Although AlphaFold2 is trained to predict the structures of individual proteins, one can jury rig AlphaFold2 to predict the structures of protein-protein complexes. We did this by concatenating two protein sequences into one and inserting a polyglycine linker of sufficient length in-between.</p><p>As an example, we used this approach to predict the structure of the barnase-barstar complex. Barnase is a ribonuclease secreted by the bacterium <a href="https://en.wikipedia.org/wiki/Bacillus_amyloliquefaciens"><em>Bacillus amyloliquefaciens</em></a>. Intracellular barnase, if active, is lethal to the cell, thus the bacterium avoids chemical suicide by expressing a potent barnase inhibitor, barstar, that tightly binds to and inhibits barnase with a blazing association rate of 10⁸ s⁻¹ M⁻¹ and sub-picomolar binding affinity (an equilibrium dissociation constant of 10⁻¹⁴ M; see, <em>e.g.</em>, <a href="https://doi.org/10.1021/bi00196a004">Buckle <em>et al.</em></a>). To predict the structure of their complex, we constructed the following sequence, connecting the two proteins using a 60-residue long polyglycine linker.</p><pre>&gt;sp|P00648|P11540|Barnase-Barstar<br>MMKMEGIALKKRLSWISVCLLVLVSAAGMLFSTAAKTETSSHKAHTEAQVINTFDGVADYLQTYHKLPDNYITKSEAQALGWVASKGNLADVAPGKSIGGDIFSNREGKLPGKSGRTWREADINYTSGFRNSDRILYSSDWLIYKTTDHYQTFTKIR<br>GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG<br>MKKAVINGEQIRSISDLHQTLKKELALPEYYGENLDALWDCLTGWVEYPLVLEWRQFEQSKQLTENGAESVLQVFREAKAEGCDITIILS</pre><p>We took care to prevent the crystal structures from being used as templates by setting the maximum template date to 1900–01–01, long before Max Perutz solved the first crystal structure of hemoglobin. AlphaFold2 predicted five very similar models; the prediction it ranked as the best is shown in Figure 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*SbFhsOgzn80FLoAyzsiURg.gif" /><figcaption><em>Figure 1. The top-ranked model of the predicted barnase-barstar complex. The barnase is at the top and the barstar is at the bottom. The AlphaFold2 prediction (blue) is superimposed onto the crystal structure (PDB id:2ZA4, orange). The polyglycine linker (gray) is predicted to be disordered.</em></figcaption></figure><p>We assessed these predicted models by the CAPRI (<strong>C</strong>ritical <strong>A</strong>ssessment of <strong>PR</strong>edicted <strong>I</strong>nteractions — <a href="https://www.capri-docking.org/">CAPRI Docking</a>) criteria, which include the following three parameters:</p><ol><li>Fraction of native contacts — fNat</li><li>Ligand RMSD — L-RMSD (the molecular docking community uses the term <strong><em>ligand</em></strong> for both a small molecule and for a smaller protein in a protein-protein complex; in our case, barstar is the ligand)</li><li>Interface RMSD — I-RMSD</li></ol><p>These parameters need to be defined with respect to a reference crystal structure. For this assessment of the barnase-barstar complex we used the PDB structure <a href="http://doi.org/10.2210/pdb2ZA4/pdb">2ZA4</a>.</p><p>A quality label may be assigned to the predicted structures based on the values of fNat, L-RMSD, and I-RMSD, as illustrated by the Figure 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*nPR7SqrmCI9XHtWIiQhjWg.png" /><figcaption><em>Figure 2. CAPRI categories for prediction qualities.</em></figcaption></figure><p>Four of the five models by AlphaFold2 are of high quality (the green rectangle in Figure 2). Interestingly, the model ranked as the best by AlphaFold2 is the only one of medium quality (the blue region in Figure 2). The CAPRI parameters for these models are summarized in the following table.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69b0c27935267376b41b7adb3d8feca5/href">https://medium.com/media/69b0c27935267376b41b7adb3d8feca5/href</a></iframe><p>The model ranked 3rd by AlphaFold2 is of the best quality based on the CAPRI criteria; Figure 3 shows its comparison to the crystal structure and Figure 4 shows its comparison to the model ranked 1st.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*NDoIoGmvNPelOMgyOAdFhw.png" /><figcaption><em>Figure 3. The model of barnase-barstar complex ranked 3rd by AlphaFold2, superimposed onto the crystal structure. Same colors are used as in Figure 1.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*cMOoz2ubSaNpdrjIDVAC_Q.png" /><figcaption><em>Figure 4. Comparison between the 1st model (blue), the 3rd model (green), and the crystal structure (orange) of barnase-barstar complex. The polyglycine linker is in gray.</em></figcaption></figure><p>Given the high degree of coevolutionary pressure between barnase and barstar across many bacteria, it is unsurprising that AlphaFold2 — which takes advantage of such coevolutionary information — was able to predict their complex with high accuracy. How well can AlphaFold2 predict other protein-protein complexes is an open and interesting question, which we will explore in future work, along with the ability to use models derived from AlphaFold2 as input structures for molecular simulations.</p><p><a href="https://www.linkedin.com/in/tarasdauzhenka/"><em>Taras Dauzhenka</em></a><em> contributed to this work.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d4dabe64cc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/roivant-technology/using-alphafold2-to-predict-the-structure-of-a-protein-protein-complex-5d4dabe64cc5">Using AlphaFold2 to Predict the Structure of a Protein-Protein Complex</a> was originally published in <a href="https://medium.com/roivant-technology">Roivant Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Remote Collaboration]]></title>
            <link>https://medium.com/roivant-technology/optimizing-remote-collaboration-3dd4d8f7e213?source=rss----dce2753b22fb---4</link>
            <guid isPermaLink="false">https://medium.com/p/3dd4d8f7e213</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Micah Grossman]]></dc:creator>
            <pubDate>Thu, 02 Sep 2021 15:58:31 GMT</pubDate>
            <atom:updated>2021-09-02T15:58:31.692Z</atom:updated>
            <content:encoded><![CDATA[<p>Full-time remote work left a large impression in 2020, cementing it as the status quo for many more companies. For people accustomed to office life, adjusting to a new way of working can be a daunting task. Learning new skills to thrive in a remote environment can feel overwhelming. The good news is many companies have been operating remotely for quite some time. By leveraging the guidance of well-operated remote teams, the home-based remote workplace can be just as fun and productive as in-office experiences.</p><p><strong>Learn From the Best</strong></p><p>I joined Roivant in November 2020 as Product Manager to help form a new all-remote division at the company: Vant Tech. We needed to establish a new culture for the team quickly, as the paradigm at the NYC office was unsuitable for remote work. No one gets points for re-inventing the wheel. GitLab was way ahead of the curve and still maintains fantastic <a href="https://about.gitlab.com/company/culture/all-remote/">documentation</a> on collaborating and managing teams remotely. We implemented most of the guidance, adjusting as needed to best fit our team. This included:</p><ul><li>Asynchronous communication must be supported.</li><li>Agenda items and meeting notes are critical for information dissemination.</li><li>People need to express their preferred methods of contact as well as optimal meeting times.</li></ul><p><strong>Walk Circles Before Lying Down</strong></p><p>One of many reasons to value dogs is their penchant for walking circles before lying down on the ground. Be it evolution, superstition, or habit, they make sure their environment is<em> </em>exactly right before settling into a good rabbit-chasing nap. Working from home is smoothest when you have a physical space dedicated to your work.</p><figure><img alt="A desktop overlooking The East Cut in San Francisco" src="https://cdn-images-1.medium.com/max/1024/1*8AedJ2e3cez5AvESxBbKew.png" /><figcaption>Wired and analog options are always dependable.</figcaption></figure><p>For myself, I need a quiet space, close to coffee and cereal, with just enough of a San Francisco city view that I can zone out and focus on a speaker’s words during a meeting. An adjustable standing desk in the kitchen fits my personality and habits best. Unless I’m doing rote data entry or watching training videos, I prefer to be standing on an anti-fatigue mat.</p><p>It’s pivotal for workers to double-check their posture and hand positioning to reduce the chance of repetitive stress injury (check out this <a href="https://ergonomictrends.com/proper-ergonomic-typing-posture-at-computer/">guide</a>). If you are regularly at a computer for 8+ hours a day, you are only hurting yourself long-term with bad form. How are you going to be the next Twitch superstar on the weekends if you cannot touch a keyboard for leisure due to carpal tunnel?</p><p><strong>Create Balance</strong></p><p>Work-life balance is a sensitive subject for some people, especially during the hiring process. The reality of all-remote work is that there is bound to be crossover between work and personal life. It can be helpful to document your work responsibilities and identify steps that require collaboration (asynchronous or real-time). This allows you to better structure your workday and maximize productivity while reducing the chance of burnout. There’s no one-size-fits-all solution. For me, managing a team means I need to be there for them when they need me. We work together to facilitate expectation management and keep track of communication preferences and known friction points; all gets captured in a “Working Norms” document in Confluence. I may temporarily turn on Slack alerts on my Apple Watch during prime work hours — some may feel that’s a step too far. It’s all about finding the right balance and ensuring that you are in control of the situation.</p><p><strong>On Water Coolers and Bathroom Breaks</strong></p><p>People often forget how many passive signals they process and use to inform how they interact with coworkers. The thing I miss most about office life is having my desk stationed next to the support team. I was a better PM by listening in to support calls as they came in, looking for patterns in problems to guide feature development, or context on a bug or request that I might be able to help with by messaging over the relevant records to the support staff.</p><p>It’s on all of us to perform introspective assessments of the types of events that could impact our actions and look for remote substitutions whenever possible. When in-office, it’s very easy to see doubt or rumors fan through a company like wildfire (starting ironically at the water cooler). Working remotely, I need to make sure I provide teammates enough opportunity for communication. People should feel free to bring up off-topic conversations and reveal what’s on their mind.</p><p>In-office I often used visual cues, like excessive bathroom breaks or seeing a person bang their head against their keyboard, as a sign that there was a situation or they felt over-stressed. Full-remote requires finesse and truly knowing your teammates to maintain a similar appearance of clairvoyance. You can’t go full helicopter parent and set a recurring hourly Slack message asking, “Are you mentally ok? Please confirm.” Leveraging passive cues leads to better people management. What is their normal writing style? Meeting attendance behavior pattern? Normal hairstyling and room cleanliness? Is anything different from expected behavior and is it a strong enough signal to trigger a direct check-in? The levels and types of signals vary from teammate to teammate. Emotional intelligence is key to maintaining a high-performing full-remote team.</p><p><strong>Socializing. Distantly.</strong></p><p>Wherever and whenever possible, try to bring teams together for social in-person meetups. Teammate-to-teammate relationships are key to all high-functioning teams I have been a part of. For remote teams, regularly hopping on Zoom to play something like a <a href="https://www.jackboxgames.com/party-pack-seven/"><em>Jackbox Party Pack</em></a> session of <em>Quiplash</em> can do so much for building relationships. People need to see their coworkers as real people and not just a choice in a dropdown when assigning tasks.</p><p><strong>Always Be Iterating</strong></p><p>Not every company will have a role or department dedicated to facilitating remote workflows. Solicit feedback regularly from your team. Find out what are the things happening that help them to fall into productive flow states. What actions do they drag their feet on? Perfection isn’t the goal. Honesty, vulnerability, and humility to change provide the best foundation to establish and grow full-remote teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dd4d8f7e213" width="1" height="1" alt=""><hr><p><a href="https://medium.com/roivant-technology/optimizing-remote-collaboration-3dd4d8f7e213">Optimizing Remote Collaboration</a> was originally published in <a href="https://medium.com/roivant-technology">Roivant Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building dag-workflows]]></title>
            <link>https://medium.com/roivant-technology/building-dag-workflows-16d5c40f7789?source=rss----dce2753b22fb---4</link>
            <guid isPermaLink="false">https://medium.com/p/16d5c40f7789</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Alec Clowes]]></dc:creator>
            <pubDate>Mon, 23 Aug 2021 18:38:46 GMT</pubDate>
            <atom:updated>2021-08-23T18:38:46.369Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building dag-workflows: a Python Workflow Execution Tool</h3><p>At Roivant, we use technology to ingest and analyze large datasets to support our mission of bringing innovative therapies to patients.</p><p>In this post, we’ll walk through the decision-making process that led to building our own <strong>workflow orchestration tool</strong>. We’ll talk about our needs and goals, the current product landscape, and the Python package we decided to build and open source.</p><p>We hope you’ll enjoy the discussion and find something useful in both our approach and the tool itself.</p><figure><img alt="Generic looking server racks" src="https://cdn-images-1.medium.com/max/1024/1*ywd_QK_ptvoPt5Tk0PAYBA.jpeg" /><figcaption>Someone needs to tell these computers what to work on. Photo by Manuel Geissinger from Pexels.</figcaption></figure><h3>Our needs</h3><p>We started our journey by looking at our past experiences and reading up on new projects. Since the mid-2010s, tools like Apache Airflow and Spark have completely changed data processing, enabling teams to operate at a new scale using open-source software. While these tools were a huge improvement, teams now want workflow tools that are self-service, freeing up engineers for more valuable work.</p><p>An article from Google engineer Adler Santos on <a href="https://cloud.google.com/blog/topics/developers-practitioners/datasets-google-cloud-introducing-our-new-reference-architecture">Datasets for Google Cloud</a> is a great example of one approach we considered: use Cloud Composer to abstract the administration of Airflow and use templating to provide guardrails in the configuration of directed acyclic graphs (DAGs). The deep analysis of features by Ian McGraw in <a href="https://medium.com/arthur-engineering/picking-a-kubernetes-orchestrator-airflow-argo-and-prefect-83539ecc69b">Picking a Kubernetes Executor</a> is a good template for reviewing requirements and making a decision based on how well they are met.</p><p>We compiled our desired features for data processing:</p><ul><li><strong>Python compatible:</strong> We use Python because data science libraries like Pandas and web frameworks like Django are easy to use and well documented.</li><li><strong>Asynchronous tasks:</strong> A tool for executing longer-running code, which is to say almost anything that cannot be completed during an API response.</li><li><strong>Triggered on-demand or on a schedule:</strong> Tasks should be triggered with API calls, by external events, or on a cron-like schedule, and we need a way to check on execution status.</li><li><strong>Support for inter-task dependencies:</strong> The ability to run tasks in parallel in a workflow makes the overall workflow faster and localizes failures.</li><li><strong>Low overhead:</strong> Tools that are easy to set up and learn, keep developers happy, and reduce the support burden.</li><li><strong>Kubernetes native:</strong> Because we deploy our applications on Kubernetes, it is convenient to have a tool that is designed for container-based orchestration.</li><li><strong>Decentralized:</strong> Defining workflows and writing orchestration code alongside the API services, data models, and scientific computing code to make dependency management, shared data models, and change management easier.</li><li><strong>Easy to test:</strong> Writing tests for common use cases should be easy, such as running SQL against a database.</li></ul><h3>Solutions considered</h3><p>We reviewed existing tools looking for something that would meet our needs. Here is a summary of our research:</p><ul><li><a href="https://man7.org/linux/man-pages/man8/cron.8.html"><strong>Cron</strong></a> is the old standby, but it does not parallelize your workflow or run across multiple servers. It’s nicely agnostic on testing, monitoring, and pretty much everything else.</li><li><a href="https://docs.celeryproject.org/"><strong>Celery</strong></a> is an established Python message-based task execution framework. It is has grown to support scheduled tasks and workflows, but the queue-based core means looking up task status and building workflows is unnecessarily difficult.</li><li><a href="https://airflow.apache.org/"><strong>Airflow</strong></a> is the market leader, popularizing the concept of DAGs in the Python community. It is a heavyweight and centralized solution, however; most developers don’t want to run it locally. It also is not Kubernetes-native: Cloud Composer abstracts the administration of Airflow but uses a legacy Celery worker to run a Kubernetes Pod. The flexibility afforded by the Python DAG definition makes enforcing common patterns difficult.</li><li><a href="https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/"><strong>Kubernetes Job/CronJob</strong></a> is easy to define and a good starting point but doesn’t handle workflows. It is agnostic to what gets run, so testing is not addressed.</li><li><a href="https://docs.dagster.io/"><strong>Dagster</strong></a> addresses many of the same testing and orchestration issues, but it mixes the orchestration metadata into the functional code, which means there is more to learn.</li><li><a href="https://docs.getdbt.com/"><strong>dbt</strong></a> is focused on advanced SQL templating, and for orchestration, they recommend their proprietary cloud or Airflow. It’s a lot to learn for a partial solution.</li><li><a href="https://meltano.com/"><strong>Meltano</strong></a> glues together Singer and dbt. Again, it uses Airflow for orchestration.</li><li><a href="https://argoproj.github.io/argo-workflows/"><strong>Argo Workflows</strong></a> implements workflows within Kubernetes, which is very promising. However, it lacks data-centric testing support and a simple local runner for development.</li><li><strong>Serverless approaches</strong> like AWS Lambda + Glue are popular but hard to simulate locally. They also split the codebase awkwardly along the needs of each component.</li></ul><h3>Our decision</h3><p>While there were many options available, none of them seemed quite right for us. Most tools were either too complicated or lacked clean Kubernetes integration. Airflow, for instance, has both shortcomings. Dagster has native Kubernetes support but a steep learning curve. It’s also opinionated about passing data and defining workflows in code, which is in conflict with our desired simplicity.</p><p>At this point, we decided to build our own lightweight wrapper for running workflows. Our vision was a tool that runs locally during development and deploys easily onto Kubernetes, with data-centric features for testing and validation. We determined there would be three main components to design: the workflow definition, the task execution, and the testing support.</p><p>We’ll introduce each of these elements in the next section in a short tutorial on using the tool we named <strong>“workflows”</strong>.</p><h3>A brief introduction</h3><p>The command line and module are workflows but the package is installed as dag-workflows like this:</p><pre>pip install dag-workflows</pre><h4>Defining DAGs and Tasks</h4><p>There are two predominant patterns for defining tasks and grouping them into a DAG. Tools like Airflow, Celery, and Dagster, define the DAG using Python code. Tools like Kubernetes and dbt use YAML. We like YAML because it is more readable and helps enforce a single way of doing things, making the configuration options clearer and easier to manage across teams. The proliferation of tools like <a href="https://github.com/chriscardillo/gusty">Gusty</a> that turn YAML into Airflow DAGs suggests many see a similar advantage. Most peculiar is the way Google’s <a href="https://github.com/GoogleCloudPlatform/public-datasets-pipelines/blob/main/README.md">Public Datasets Pipelines</a> uses Jinga to generate the Python code from YAML.</p><p>We follow the pattern of grouping individual tasks into a DAG by representing each task as a file in a folder representing the DAG. Like Gusty and other tools, we put the YAML configuration in a comment at the top of each file. The individual task files can be.sql, .py, or .yaml files. A SQL task looks like this:</p><pre>/*<br> description: Make a table<br> type: sql<br> inputs: []<br> */<br> CREATE TABLE IF NOT EXISTS example AS<br> SELECT &#39;test&#39; AS name, 1 AS value;</pre><p>And a Python task should have a run method that looks like this:</p><pre>&quot;&quot;&quot;<br>description: Copy a file<br>type: python<br>inputs:<br>- other_task.sql<br>&quot;&quot;&quot;<br>import shutil</pre><pre>def run(context):<br>    shutil.copy(&#39;file_A&#39;, &#39;file_B&#39;)</pre><p>You’ll notice that the YAML has a field called inputs; this is where you list the tasks which are predecessors and should run first.</p><h4>Running the DAG</h4><p>After writing your tasks, the next step is to run them. We designed workflows to support multiple execution models, two of which handle scheduling and parallelization:</p><ul><li>The <strong>Kubernetes scheduler</strong> runs each task as a Kubernetes Pod. It triggers DAGs on a cron-like schedule and runs tasks as their dependencies are satisfied. It uses a PostgreSQL database to keep track of DAG and task runs.</li><li>The <strong>worker scheduler</strong> uses the same scheduling logic but runs tasks as a subprocess. Multiple workers can be run to parallelize execution.</li><li>For <strong>local development</strong>, the command line workflows run interface is used to run tasks locally. The same interface is used by the schedulers when running a single task.</li><li><strong>Third-party executors</strong> such as good ol’ cron and Airflow can use CLI runner as well. In Python, they can introspect the DAG object and call the execute method on tasks directly.</li></ul><figure><img alt="Diagram of the scheduler and runner components of workflows." src="https://cdn-images-1.medium.com/max/1024/1*11Z8W8BFAQ377lNYlZYlrQ.png" /></figure><p>To run the local executor, use the command line. The first argument is a configuration file which, at minimum, tells workflows what folder to look in for DAGs:</p><pre>workflows dags.config run dag_name</pre><p>To run the worker or Kubernetes schedulers, you need to provide a cron-like schedule for each DAGs in a YAML file, along with executor specific configurations like this:</p><pre>description: Example DAG<br>schedule: &#39;5 */4 * * *&#39;  # every four hours at five after<br>worker_config:<br>    kube_image: &quot;my_image:latest&quot;</pre><p>The scheduler requires access to a PostgreSQL database and is run from the command line like this. The scheduler type to use is specified in the last argument:</p><pre>export DATABASE_URL=postgres://localhost/workflows<br>workflows dags.config schedule kubernetes</pre><h4>Writing Tests</h4><p>An important requirement for us was easy testing of tasks. To support testing, we built a pytest fixture that supports running a task or DAG, and handles test database setup and teardown in the special case of SQL tasks. Our fixture utilizes pytest-django to create the database, and while you can choose to use <a href="http://xn--djangoprojet-yrb.com/">Django</a> with workflows, it is not required.</p><p>This example test covers a SQL task. It gets the task, sets up the input tables with test data, and executes the task. It asserts that the output matches the expected values:</p><pre>from example_project import config<br></pre><pre>def test_calculate_trades(workflows):<br>    task = config.DAGS[&quot;trader_bot&quot;].get_task(<br>        &quot;calculate_trades.sql&quot;)<br>    initial_data = {<br>        &quot;stock_prices&quot;: [<br>            {&quot;date&quot;: &quot;2020-01-01&quot;, &quot;close&quot;: 34},<br>            {&quot;date&quot;: &quot;2020-01-02&quot;, &quot;close&quot;: 43}<br>        ],<br>        &quot;limits&quot;: [{&quot;max_bid&quot;: 100}],<br>    }<br>    workflows.setup_task_inputs(task, initial_data)</pre><pre>    results = workflows.execute_task(task)</pre><pre>    assert len(results[&quot;new_trades&quot;]) == 2<br>    assert results[&quot;new_trades&quot;][0][&quot;limit_price&quot;] == 134</pre><h3>Learn More</h3><p>Thanks for taking the time to read about workflows! Here’s some suggested reading that might be of interest.</p><ul><li>See <a href="https://dag-workflows.readthedocs.io/en/latest/using_workflows.html">Using Workflows</a> on Read the Docs for a comprehensive introduction. In particular, read about writing custom <a href="https://dag-workflows.readthedocs.io/en/latest/task_types.html">task types</a> to support your use cases and using <a href="https://dag-workflows.readthedocs.io/en/latest/output_types.html">outputs</a> to perform data validations.</li><li>Read <a href="https://medium.com/roivant-technology/introducing-the-roivant-technology-blog-201972bbe49f">Introducing the Roivant Technology Blog</a></li><li>Work with us! View our <a href="https://www.roivantcareers.com/job/senior-software-engineer-vant-technology-technology-us-ny-new-york-151-west-42nd-s-4-1746959/">open positions</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16d5c40f7789" width="1" height="1" alt=""><hr><p><a href="https://medium.com/roivant-technology/building-dag-workflows-16d5c40f7789">Building dag-workflows</a> was originally published in <a href="https://medium.com/roivant-technology">Roivant Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Roivant Technology Blog]]></title>
            <link>https://medium.com/roivant-technology/introducing-the-roivant-technology-blog-201972bbe49f?source=rss----dce2753b22fb---4</link>
            <guid isPermaLink="false">https://medium.com/p/201972bbe49f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[pharmaceuticals-industry]]></category>
            <dc:creator><![CDATA[Andrew Ward]]></dc:creator>
            <pubDate>Fri, 30 Jul 2021 17:14:49 GMT</pubDate>
            <atom:updated>2021-07-30T17:14:49.658Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Our mission at Roivant is to</strong> <strong>bring innovative therapies to the patients who need them, <em>faster</em></strong>.</h4><p>We believe technology plays a central role in re-thinking the traditional pharma approach. The products we’re building can accelerate the pace at which life-saving therapies make it to patients. Working across the entire spectrum of the pharma lifecycle — including discovery, development, and commercialization — we’re using the power of technology to reshape how therapies are engineered.</p><p>In this blog, we’ll highlight some of the projects we’re working on through articles contributed by members of our tech teams, including:</p><ul><li><strong>Identifying the Under-served</strong>: Assembling sufficient data to understand which populations are under-served by the current standard of care.</li><li><strong>Understanding the Data</strong>: Building software to un-silo and make sense of clinical data.</li><li><strong>Improving the Process</strong>: Making clinical trials faster, less error-prone, and more patient-friendly.</li><li><strong>Accelerating Discovery</strong>: Identifying therapeutic candidates with machine learning and physics-based simulation.</li><li><strong>How We Work:</strong> What it’s like to be a technology team member at Roivant.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=201972bbe49f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/roivant-technology/introducing-the-roivant-technology-blog-201972bbe49f">Introducing the Roivant Technology Blog</a> was originally published in <a href="https://medium.com/roivant-technology">Roivant Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>