<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<div id="editbody1">
<div style="font-size: 10pt; font-family: Verdana,Geneva,sans-serif;">
<p>Hi Jacob,</p>
<p>Thanks for leading the discussion. </p>
<p>You may have to wait until early Jan for everyone to get back from the holidays and respond.</p>
<p>Also, I think, it may not be possible to get away without improving the flow and readability of the manuscript.</p>
<p>Here are my comments on model sharing and license </p>
<p>Indeed often models are hard to locate. Hence in our reproducibility study ( Tiwari et al. 2021, <a href="https://doi.org/10.15252/msb.20209982" target="_blank" rel="noopener noreferrer">https://doi.org/10.15252/msb.20209982</a>), we strongly recommend authors to make their models public, but more specifically through public repositories such as BioModels (<a href="https://www.ebi.ac.uk/biomodels" target="_blank" rel="noopener noreferrer">https://www.ebi.ac.uk/biomodels</a>). We recommend authors to submit model codes, parameter sets, and simulation conditions needed to reproduce simulation studies.</p>
<p>BioModels provides model curation and annotation service, where the models' reproducibility is assessed and annotated with controlled vocabularies. The BioModels offers sophisticated search engines to search and locate models and model components (<a href="https://www.ebi.ac.uk/biomodels/parameterSearch" target="_blank" rel="noopener noreferrer">https://www.ebi.ac.uk/biomodels/parameterSearch</a>). Overall this will greatly facilitate model reuse.</p>
<p>More importantly, all models are disseminated under the permissive CC0 license in BioModels. This is because it is crucial to openly release the models developed through public funding. Also, curation services done at BioModels are supported by public funding. </p>
<p>Although few users suggested we use CC-BY, we decided to continue with CC0. However, we strongly recommend our users to properly cite the model when reused and most researchers normally do. Also, If a modeler collects and integrates components from several hundred models, it may become difficult to properly acknowledge them all. </p>
<p>Best regards</p>
<p>Sheriff</p>
<p><br /></p>
<p id="v1reply-intro">On 2021-12-27 10:59, Jacob Barhak wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="v1replybody1">
<div dir="ltr">Greetings Paper contributors,
<div> </div>
<div>Especially Alex, Hana, William, and Sheriff should read this since I name them below. <br />
<div> </div>
<div>To move things forwards I started editing the paper and am sending an update of our checklist with responses to the reviewers. Please check the list if you think you want to contribute more to the paper - it is open for editing - the time window will close once we answered all reviewers - however, please focus on what reviewers asked for and do nto add anything else - I am restraining myself from adding more otherwise there will be no end to editing. </div>
<div> </div>
<div>The answers for the reviews so far are:</div>
<div> </div>
<div>1. We thank reviewer 1 for pointing out the papers - we added those references into the discussion. Especially we thank the reviewer for pointing out the (Viceconti et al., 2019) paper - it is indeed unique in its attempt to classify and quantify model credibility with some good examples. We agree it should be cited in our paper since it is an important step forward. </div>
<div> </div>
<div>2. TBD - Alex will provide an answer to the reviewer - he confirmed he got the message</div>
<div> </div>
<div>3. I suggest that the reviewer will have the following answer to the request to focus on COVID-19 in the title. We thank the reviewer for the suggestion to focus on COVId-19 and put it in the title. However, we intend the paper to cover more than just one disease - in fact we have examples in the paper that span diabetes, heart disease as well as COVID - We did add recent COVID-19 models as the reviewer suggested, yet we would lie to keep the broader approach and keep the title without change. </div>
<div> </div>
<div>4. TBD - I have no idea for more graphics - this is still an open item - please suggest solutions.</div>
<div> </div>
<div>5. The "Contribution to the Field Statement" section was revised. Any contributor is welcome to edit it further.</div>
<div> </div>
<div>6. Regarding a major rewrite I suggest the following answer to the reviewer: "We thank the reviewer for advice to improve the paper readability and indeed the group is aware that there are many ideas presented in the paper - yet this is expected from a large and diverse group that provided contributions. The reviewer should be aware that we made every attempt to keep all the ideas intact and what seems sometimes as noise, is actually a choir where every voice is important. This choire attempts to explain the modeling complexity. We did have attempts to reduce the work to something easier to digest - see the versions we quote in the paper. However, those versions were never approved by all contributors as necessary for publication - this is actually the law. What the reviewer saw was a compromise that keeps all ideas as best we could while providing a summary that allows readers to jump to sections of interest. Specifically table 1 is perhaps the most important artifact in the paper. and do ask the reviewer to weigh the importance of its quick publication. We can spend months on trying to revise the paper and reach agreement, yet this will probably not change the core of the paper and will waste resources on 18 contributors needing to constantly change things. Therefore we ask that the reviewer consider the benefit of releasing this information fast so it will make an impact rather than sending is back to rewrites that will delay impact in the name of style - an agreement among such a large and diverse group has a weight and the discussions around this paper are transparent so that readers can go back and clarify things if needed. " - beyond this response, if someone wants to spend time and improve the introduction without omitting ideas or references other than their own, then please let us know - I am open to suggestions.</div>
<div> </div>
<div>7. The answer above in 6. should answer the reviewer that requested changing the introduction - however, if anyone has another suggestion, I am open. </div>
<div> </div>
<div>8. I modified the specific section that the reviewer asked to address. Reviewer 2 wants additional discussion around the "reproducibility crisis" section and asks a valid question about expectations we should address - ""Computational biomedical modeling... was expected to be less affected by the reproducibility crisis." Is this true, and why would it be so? " - My answer to the reviewer is that unlike biological processes that have random nature and experiments would not repeat if repeated, while computer software should be deterministic and it should be repeatable if designed well. Unfortunately we are not experiencing this promise. If anyone wants to expand the discussion, please feel free to do so. </div>
<div> </div>
<div>
<div>9. TBD - See also point 12. below. A discussion was started in this thread: <a href="https://lists.simtk.org/pipermail/vp-integration-subgroup/2021-December/000324.html" target="_blank" rel="noopener noreferrer">https://lists.simtk.org/pipermail/vp-integration-subgroup/2021-December/000324.html</a> - suggested discussors are William, and Sheriff - yet anyone else is welcome to join and contributes. So far no confirmation or response was recorded.</div>
<div> </div>
<div>10. A discussion was started in this thread: <a href="https://lists.simtk.org/pipermail/vp-integration-subgroup/2021-December/000325.html" target="_blank" rel="noopener noreferrer">https://lists.simtk.org/pipermail/vp-integration-subgroup/2021-December/000325.html</a> - suggested discussor is Hana, So far no confirmation or response was recorded.</div>
<div> </div>
<div>11. TBD - Reviewer 2 asks that we better handle the section on Data availability and measurement definitions: I think we need to emphasize solutions and separate them from issues that may not be solvable. However, Hana and I wrote most of this section with some text from Alex I believe, so we perhaps should meet and discuss how to improve it - it is indeed long and needs fixing. Ideas from anyone are welcome.</div>
<div> </div>
<div>12. TBD - See - point 9 above - A discussion was started in this thread: <a href="https://lists.simtk.org/pipermail/vp-integration-subgroup/2021-December/000324.html" target="_blank" rel="noopener noreferrer">https://lists.simtk.org/pipermail/vp-integration-subgroup/2021-December/000324.html</a> - suggested discussors are William, and Sheriff - yet anyone else is welcome to join and contributes. So far no confirmation or response was recorded.</div>
<div> </div>
</div>
<div>13. TBD - Reviewer 2 asks to handle the Model Application and Implementation Barriers section. We should decide what to do there, the section may need expansion since the ideas there are solid, yet the section is short so perhaps enhancing it makes better sense. I am open to suggestions.</div>
<div> </div>
<div>The revised paper is available in: </div>
<div> </div>
<div><a href="https://docs.google.com/document/d/1IMEgmdNkx-EsnOjGuegpenSIMmKIkK00Lc8Gred3QxM/edit?usp=sharing" target="_blank" rel="noopener noreferrer">https://docs.google.com/document/d/1IMEgmdNkx-EsnOjGuegpenSIMmKIkK00Lc8Gred3QxM/edit?usp=sharing</a></div>
<div> </div>
<div>I ask that all contributors interested in making modifications write those ideas on the mailing list so that we can move forward with this paper. </div>
<div> </div>
<div>I really hope some of you will use the time before the year ends to advance this. </div>
<div> </div>
<div> </div>
<div> Jacob</div>
<div> </div>
<div> </div>
<div> </div>
</div>
</div>
<br />
<div class="v1v1gmail_quote">
<div class="v1v1gmail_attr" dir="ltr">On Mon, Dec 20, 2021 at 5:50 PM Jacob Barhak <<a href="mailto:jacob.barhak@gmail.com" rel="noreferrer">jacob.barhak@gmail.com</a>> wrote:</div>
<blockquote class="v1v1gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;">
<div dir="ltr">Thanks Alex,
<div> </div>
<div>The paper opened back for editing. If someone really feels they have to edit and they are not on the list - let me know and I will add them to the list of editors. - yet for now - let us form a plan to answer the reviewers and only then touch text again - otherwise this will get out of hand since there are so many of us. </div>
<div> </div>
<div>I appreciate your support. </div>
<div> </div>
<div> Jacob</div>
</div>
<br />
<div class="v1v1gmail_quote">
<div class="v1v1gmail_attr" dir="ltr">On Mon, Dec 20, 2021 at 3:50 PM Alexander Kulesza <<a href="mailto:alexander.kulesza@novadiscovery.com" rel="noreferrer">alexander.kulesza@novadiscovery.com</a>> wrote:</div>
<blockquote class="v1v1gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;">
<div dir="ltr">
<div dir="ltr">Dear Jacob, dear all,
<div>Yes will take care of 2. and happy to help wherever I can. </div>
<div>Best </div>
</div>
<br />
<div class="v1v1gmail_quote">
<div class="v1v1gmail_attr" dir="ltr">On Sun, 19 Dec 2021 at 03:10, Jacob Barhak <<a href="mailto:jacob.barhak@gmail.com" rel="noreferrer">jacob.barhak@gmail.com</a>> wrote:</div>
<blockquote class="v1v1gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;">
<div dir="auto">
<div dir="ltr"><br />
<div>Greetings to the paper contributors,</div>
<div> </div>
<div>You may have seen my other message where I posted the reviews to our paper. I am sending those again below to start a new thread discussing possible revisions.</div>
<div> </div>
<div>Here is a checklist for revisions required:</div>
<div> </div>
<div>
<ol>
<li> We should discuss the references that reviewer 1 raised and add them as reference</li>
<li>Reviewer 1 asked for more discussion around V&V40 - I believe Alex added the text there originally - Alex do you think you can address the request of the reviewer?</li>
<li>Reviewer 1 asked to focus on COVID-19 at the title - I am not sure we wish to limit our scope since many of our ideas are applicable far beyond COVID-19 - I leave it up for discussion in the group on how to address this request by the reviewer </li>
<li>Reviewer 1 asked for additional graphics - I am unsure how to address this beyond ur current diagram - ideas will help</li>
<li>We need to check the "Contribution to the field" section for grammar and spelling - if someone can contribute more elegant text - now is the time - I looked over it now and found no issues - yet I may have missed something - this section may have been missed since it was added last and perhaps vetted less than other sections. Also Reviewer 2 asked for grammar corrections, so it is worthwhile proof reading the paper as a whole.</li>
<li>Reviewer 2 asks for major rewrite to emphasize why the problems are there - I think we should explain that the core of the paper is the table and perhaps emphasize it in the paper beyond what the current text - we also should reply to the reviewer and explain that the paper is composed of contributions from a large group and we made an effort to include every voice in the choir - each of those voices is important and needs to be preserved - hopefully it will convince the reviewer that change we will add will be sufficient</li>
<li>Reviewer 2 asks to revise the introduction - I believe some changes are possible - yet the introduction includes contributions from many authors - at least 10 - and I fear losing something important someone contributed - if someone has an idea on how to address this reviewer without a painful transformation, please reply to this message.</li>
<li> Reviewer 2 wants additional discussion around the "reproducibility crisis" section and asks a valid question about expectations we should address - ""Computational biomedical modeling... was expected to be less affected by the reproducibility crisis." Is this true, and why would it be so? " - My answer to the reviewer is that unlike biological processes that have random nature and experiments would not repeat if repeated, while computer software should be deterministic and it should be repeatable if designed well. Unfortunately we are not experiencing this promise - yet I believe the reviewer wants more discussion beyond this section so I am happy to discuss this.</li>
<li>Reviewer 2- writes: "Models are Hard to Locate: Are the authors suggesting that entire simulation workflows, from model construction to analysis, should be publicly available? At what point does one consider intellectual property? Do the authors advocate for such extensive publishing for all models, or only ones that are intended to be widely re-used? - those are important points we need to discuss - we need to better explain the difficulties we are having when creating models and the reviewer is absolutely correct about expanding the discussion to IP - I suggest we create a thread for this discussion and reference it - I suggest it we merged with the licensing issue that I will address later - there is a strong connection there - the reviewer was very observant and sees the bigger problem. However,we need to eventually distill our discussion to recommendations that will inline. </li>
<li>Reviewer 2 asks that we fix the unit standardization section - I believe Hana and myself were the largest contributors there - Hana - I will start a discussion on that topic in a separate email where we can publicly discuss how to fix this - others will be welcome to contribute. </li>
<li>Reviewer 2 asks that we better handle the section on Data availability and measurement definitions: in think we need to emphasize solutions and separate it from issues that may not be solvable. Ideas are welcome.</li>
<li>Reviewer 2 asks good questions with regards to licensing following our text- I personally have good answers to the reviewer and William and I had some discussion on the topic in this list I suggest we expand this discussion in a separate thread - hopefully William and perhaps others will join the discussion. This discussion should also address the IP issues raised by the reviewer for the "models are hard to locate section."</li>
<li>Reviewer 2 asks to handle the Model Application and Implementation Barriers section. We should decide what to do there, the section may need expansion since the ideas there are solid, yet the section is short so perhaps enhancing it makes better sense. I am open to suggestions. </li>
</ol>
<div dir="auto"> </div>
<div>Those are the items I located and my suggestions. It seems we need attention from Alex, Hana, myself and william. However, anyone on the list is welcome to participate and suggest changes.</div>
<div dir="auto"> </div>
<div dir="auto">I will start the discussion threads on specific topics. Hopefully we can get it done quickly.</div>
<div dir="auto"> </div>
<div dir="auto"> Jacob</div>
<div dir="auto"> </div>
<div dir="auto"> </div>
<div> </div>
</div>
<div> </div>
<div> </div>
<div> </div>
<div>- </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div>########### Original Reviews #############</div>
<div> </div>
<div>
<div>There are 2 reviews - both require major changes. I am copying the relevant text below. If more appear, I will let you know, yet I only got this message today although the reviews are dated a few days ago. </div>
<div> </div>
<div>Reviewer 1: </div>
<div><span style="color: #3e3d40; font-family: Lucida Grande, Trebuchet MS, Arial, sans-serif;"><span style="font-size: 12px; outline-color: initial; outline-style: initial;">Recommendation for the Editor: </span></span>Substantial revision is required</div>
<div> </div>
<div>Please list your revision requests for the authors and provide your detailed comments, including highlighting limitations and strengths of the review. If you have additional comments based on Q2 and Q3 you can add them as well.</div>
<div> </div>
<div>Karr and co-authors made an interesting and exaustive point about the reproducibility crisis that leads to inability to reuse and integrate models, especially about COVID-19 disease.<br style="outline: 0px;" />Within the manuscript some typos and missing information are present.<br style="outline: 0px;" />I'd suggest the authors to revise the entire manuscript especially in terms of the state of the art, revising and updating the most relevant examples of computational models dealing with COVID-19 and in general about some semi-standardised proposals about the pipeline to follow for the verification and validation of model credibility. In particular, the authors failed to mention and cite some major results on in silico modeling about COVID-19 up to now. See for example:<br style="outline: 0px;" />a."In silico trial to test COVID-19 candidate vaccines: a case study with UISS platform", Russo, G., Pennisi, M., Fichera, E., ...Viceconti, M., Pappalardo, F., BMC Bioinformatics, 2020, 21, 527.<br style="outline: 0px;" />b. Russo G, Di Salvatore V, Sgroi G, Parasiliti Palumbo GA, Reche PA, Pappalardo F. "A multi-step and multi-scale bioinformatic protocol to investigate potential SARS-CoV-2 vaccine targets" [published online ahead of print, 2021 Oct 5]. Brief Bioinform. 2021;bbab403. doi:10.1093/bib/bbab403.<br style="outline: 0px;" />Moreover, when the authors mention ASME V&V40 procedure, it could be useful to spend few words about the model credibility pipeline drawn for predictive models in biomedicine, such as the one suggested in "Credibility of in Silico Trial Technologies-A Theoretical Framing", Viceconti, M., Juarez, M.A., Curreli, C., ...Russo, G., Pappalardo, F., IEEE Journal of Biomedical and Health Informatics, 2020, 24(1), pp. 4–13, 8884189.<br style="outline: 0px;" />For this specific aspect, the authors should talk about "specific question of interest" and not "specific purpose" in the paragraph called "Credibility of Models" to follow in such a way a standardised language.<br style="outline: 0px;" />Moreover, the authors should refer to COVID-19 also in the title, with a specific mention about the fact that the main topic of model integration in computational biology will be discussed inside the COVID-19 context.<br style="outline: 0px;" />Furthermore, for the model key concepts such as Reusability-Extensibility-Extractability-Portability the authors should described and outlined through a graphical sketch or visual representation that summarises these key point.<br style="outline: 0px;" />The authors should also fix some grammar and writing typos present in the "Contribution to the field" section.</div>
<div> </div>
<div>
<div style="border-top: 1px solid #d9d9d9; outline: 0px;">
<div style="padding-top: 15px; outline: 0px;">
<div style="outline: 0px;">a. Is the quality of the figures and tables satisfactory?<br style="outline: 0px;" />- No<br style="outline: 0px;" /><br style="outline: 0px;" />b. Does the reference list cover the relevant literature adequately and in an unbiased manner?<br style="outline: 0px;" />- No<br style="outline: 0px;" /><br style="outline: 0px;" />c. Does this manuscript refer only to published data? (unpublished or original data is not allowed for this article type)<br style="outline: 0px;" />- Yes<br style="outline: 0px;" /><br style="outline: 0px;" />d. Does the review include a balanced, comprehensive, and critical view of the research area?<br style="outline: 0px;" />- Yes</div>
</div>
<div id="v1v1gmail-m_7395306204832809451gmail-m_4211070854393467339gmail-m_8247746808502553674m_6090386399552853868m_5335031614454254218m_6805043092736084016m_476535936230498237gmail-m_-8345716752565666099gmail-7672" style="outline: 0px;">
<div style="padding: 5px 0px 5px 5px; outline: 0px;">
<div style="outline: 0px;"> </div>
</div>
</div>
</div>
<div style="height: 20px; margin-top: 10px; margin-left: 20px; outline: 0px;"> </div>
</div>
<div style="height: 20px; margin-top: 10px; margin-left: 20px; outline: 0px;"> </div>
<div style="height: 20px; margin-top: 10px; margin-left: 20px; outline: 0px;">Reviewer 2</div>
<div style="height: 20px; margin-top: 10px; margin-left: 20px; outline: 0px;"> </div>
<div style="height: 20px; margin-top: 10px; margin-left: 20px; outline: 0px;">Please list your revision requests for the authors and provide your detailed comments, including highlighting limitations and strengths of the review. If you have additional comments based on Q2 and Q3 you can add them as well.</div>
<div style="height: 20px; margin-top: 10px; margin-left: 20px; outline: 0px;"> </div>
<div> </div>
<div>The article often reads as a stream-of-consciousness account of the discussions that took place but lacks a clear thesis or recommendations. It is not clear what, if anything, the authors are advocating for. It is not always clear why the issues being discussed are problematic, or that they can be reasonably addressed. Some of the issues raised are indeed important and should be discussed, but the paper lacks focus and does not tell a cohesive story. I believe this manuscript requires a major re-write to be suitable for publication. The authors should consider narrowing the scope of the discussion and focusing on a cohesive set of recommendations or open questions. More specifically, I make a few suggestions below:<br style="outline: 0px;" /><br style="outline: 0px;" />Major comments<br style="outline: 0px;" />1. The introduction is long and repeats itself (e.g., "much less is known about how viral infections spread throughout the body..." is repeated verbatim). It is not clear from the introduction what the main goal of the paper is or why the "reproducibility crisis" is truly a crisis. Why is the discussion of composition and black/white box models relevant to the introduction? Further, this section is subtitled "the promise of modeling", which does not seem to match the content.<br style="outline: 0px;" />2. The Reproducibility Crisis: "Computational biomedical modeling... was expected to be less affected by the reproducibility crisis." Is this true, and why would it be so? One would think that more complex models would suffer more from a lack of reproducibility. It may be helpful to define what exactly the "reproducibility crisis" refers to.<br style="outline: 0px;" />3. Models are Hard to Locate: Are the authors suggesting that entire simulation workflows, from model construction to analysis, should be publicly available? At what point does one consider intellectual property? Do the authors advocate for such extensive publishing for all models, or only ones that are intended to be widely re-used?<br style="outline: 0px;" />4. Unit standardization: The conversion from PFU or TCID50 to individual virions is likely to differ across viruses – are the authors focused on COVID here? Are the authors advocating for a standard conversion factor? It is not clear what the purpose of this discussion is. As the authors mention, different scales require different units. Even at a single scale, different models may require different units for numerical reasons. It is not clear what the authors are advocating for here.<br style="outline: 0px;" />5. Data availability and measurement definitions: This section seems to outline limitations of available data, but again makes no recommendations or proposed solution to any of the issues raised. Is this the intention? Most of the issues raised here reflect limitations of experimental science or data privacy, which likely cannot be meaningfully addressed by the modeling community.<br style="outline: 0px;" />6. Models are Not Consistently Licensed...: Are the authors implying here that all modeling work should be published with no rights reserved? Is it reasonable to expect modelers to make their work freely usable by others for profit? Is it reasonable for institutions to allow this? How much does this really contribute to reproducibility and utility?<br style="outline: 0px;" />7. Model Application and Implementation Barriers: This section seems unnecessary and out of place.<br style="outline: 0px;" />8. There are grammar and punctuation errors scattered throughout; please edit carefully.</div>
<div> </div>
<div> </div>
<div>a. Is the quality of the figures and tables satisfactory?<br style="outline: 0px;" />- Not Applicable<br style="outline: 0px;" /><br style="outline: 0px;" />b. Does the reference list cover the relevant literature adequately and in an unbiased manner?<br style="outline: 0px;" />- Yes<br style="outline: 0px;" /><br style="outline: 0px;" />c. Does this manuscript refer only to published data? (unpublished or original data is not allowed for this article type)<br style="outline: 0px;" />- Yes<br style="outline: 0px;" /><br style="outline: 0px;" />d. Does the review include a balanced, comprehensive, and critical view of the research area?<br style="outline: 0px;" />No answer given.</div>
<div> </div>
<div> </div>
<div>========</div>
</div>
</div>
</div>
_______________________________________________<br />Vp-reproduce-subgroup mailing list<br /><a href="mailto:Vp-reproduce-subgroup@lists.simtk.org" rel="noreferrer">Vp-reproduce-subgroup@lists.simtk.org</a><br /><a href="https://lists.simtk.org/mailman/listinfo/vp-reproduce-subgroup" target="_blank" rel="noopener noreferrer">https://lists.simtk.org/mailman/listinfo/vp-reproduce-subgroup</a></blockquote>
</div>
<br clear="all" />
<div> </div>
-- <br />
<div dir="ltr">
<div dir="ltr">
<div style="font-family: sans-serif; font-size: 13px; white-space: pre-wrap; padding: 2px 0px 2px 13px; color: #36394f;">
<div style="font-stretch: normal; line-height: normal; white-space: normal; padding: 2px 0px; color: #232349;">Alexander Kulesza</div>
<div style="font-stretch: normal; font-size: 11px; line-height: normal; white-space: normal; padding: 2px 0px; color: #344673;">Team leader</div>
<div style="font-stretch: normal; font-size: 11px; line-height: normal; white-space: normal; padding: 2px 0px; color: #5287bd;">Modeling & simulation / Biomodeling</div>
<div style="font-stretch: normal; font-size: 11px; line-height: normal; white-space: normal; padding: 2px 0px; color: #808696;"><a style="color: #808696;" href="mailto:alexander.kulesza@novadiscovery.com" rel="noreferrer">alexander.kulesza@novadiscovery.com</a></div>
<div style="font-stretch: normal; font-size: 11px; line-height: normal; white-space: normal; padding: 2px 0px; color: #808696;">+33 7 82 92 44 62</div>
<div style="white-space: normal; width: 100px; margin: 15px 0px; font-size: 28px; color: #232349;">
<div style="font-family: Montserrat,arial; font-weight: 600; letter-spacing: -1px;">nova</div>
<div style="font-size: 9px;">DISCOVERY</div>
</div>
<div style="color: #333333; font-stretch: normal; font-size: 11px; line-height: normal; white-space: normal; padding: 2px 0px; margin: 0px;"><a style="color: #808696;" title="Visit our website" href="http://www.novadiscovery.com/" target="_blank" rel="noopener noreferrer">www.novadiscovery.com</a></div>
<div style="font-stretch: normal; font-size: 11px; line-height: normal; white-space: normal; padding: 2px 0px; color: #808696;">1 Place Verrazzano, 69009 Lyon<br />+33 9 72 53 13 01</div>
</div>
</div>
</div>
</div>
<br /><em style="color: #bbbbbb; font-family: sans-serif; font-size: 10px; text-align: justify;">This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.</em></blockquote>
</div>
</blockquote>
</div>
</div>
<br />
<div class="v1pre">_______________________________________________<br />Vp-integration-subgroup mailing list<br /><a href="mailto:Vp-integration-subgroup@lists.simtk.org" rel="noreferrer">Vp-integration-subgroup@lists.simtk.org</a><br /><a href="https://lists.simtk.org/mailman/listinfo/vp-integration-subgroup" target="_blank" rel="noopener noreferrer">https://lists.simtk.org/mailman/listinfo/vp-integration-subgroup</a></div>
</blockquote>
<p><br /></p>
<div id="v1_rc_sig"> </div>
</div>
</div>
</body></html>