<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> </head> <body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <div>Hi,</div> <div><br> </div> <div>Thanks all for the updates! This sounds good. We will discuss then at Uppsala, what we want to add in addition to what you do. We'll aim at installing in both places.</div> <div><br> </div> <div>Our parser requires Dynet. Lately we have been installing that locally, since system versions haven't been in sync, and installation is much easier than it used to be. But if the infrastructure task force could consider adding an NLPL Dynet module, that would be useful, at least to us. The latest version should work for us.</div> <div><br> </div> <div>Best,</div> <div>Sara</div> <div><br> </div> <br> <div> <div>7 nov 2019 kl. 13:04 skrev Stephan Oepen <<a href="mailto:oe@ifi.uio.no">oe@ifi.uio.no</a>></div> <div>:</div> <br class="Apple-interchange-newline"> <blockquote type="cite"> <div> <div dir="auto">dear all,</div> </div> <div dir="auto"><br> </div> <div dir="auto">in general, we are aiming for greatly increased uniformity in this round, i.e. the same modules in the same versions on both Puhti and Saga. thus, my recommendation would be fewer modules, if need be, but always think both systems.</div> <div dir="auto"><br> </div> <div dir="auto">we are currently working to provision a uniform set of ’base‘ modules, e.g. NumPy, SciPy, Gensim, NLTK, spaCy, PyTorch, Keras, TensorFlow, CoreNLP, and StanfordNLP. in case your plans for parsing modules require anything in addition to these, please let the infrastructure task force know quickly. we are currently standardizing on Python 3.7; if you absolutely need other versions, please get in touch!</div> <div dir="auto"><br> </div> <div dir="auto">even though several of the above are also available as system modules (i.e. not maintained by NLPL), i would encourage you to build NLPL modules on top of the NLPL versions of these libraries, again for uniformity across systems. the above basic collection is near-complete on Saga, and we expect to put the same NLPL modules in place in Puhti this coming week.</div> <div dir="auto"><br> </div> <div dir="auto">please note some updates to the software installation guide, also regarding ad-hoc versioning (e.g. ‘201911’) where there are no externally defined versions:</div> <div dir="auto"><br> </div> <div dir="auto"> <div><a href="http://wiki.nlpl.eu/index.php/Infrastructure/installation/guide">http://wiki.nlpl.eu/index.php/Infrastructure/installation/guide</a></div> <br> </div> <div dir="auto">all best, oe</div> <div dir="auto"><br> </div> <div><br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Thu, 7 Nov 2019 at 12:45 Tiedemann, Jörg <<a href="mailto:jorg.tiedemann@helsinki.fi">jorg.tiedemann@helsinki.fi</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div style="word-wrap:break-word"> <div>Hi,</div> <div><br> </div> <div>I will probably package the old udpipe into a module for some compatibility reasons. If you want to make one for udpipe future then this would be great as well (I actually don’t really know what the status of that package is at the moment).</div> <div><br> </div> <div> <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word; "> <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word; "> <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word; "> <div style="word-wrap:break-word"><span>All the best,</span></div> <div style="word-wrap:break-word">Jörg</div> <div style="word-wrap:break-word"><span><br> </span></div> <div style="word-wrap:break-word"><span>********************************************************************************************</span></div> </div> </div> </div> </div> </div> <div style="word-wrap:break-word"> <div> <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word; "> <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word; "> <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word; "> <div style="word-wrap:break-word"><br> <span>Jörg Tiedemann</span></div> <div style="word-wrap:break-word"><span>Language Technology<span style="white-space:pre-wrap"> </span></span><a href="https://blogs.helsinki.fi/language-technology/" target="_blank">https://blogs.helsinki.fi/language-technology/</a></div> <div><span>University of Helsinki</span></div> </div> </div> </div> </div> <br> <div> <blockquote type="cite"> <div>On 07 Nov 2019, at 12:50, Filip Ginter <<a href="mailto:figint@utu.fi" target="_blank">figint@utu.fi</a>> wrote:</div> <br> <div> <div dir="ltr"> <div>Hi Sara</div> <div><br> </div> <div>OK. We will look into packaging the current parser pipeline we have as a puhti module. We will also look into packaging Udify into the pipeline, the module structure would be the same then.</div> <div><br> </div> <div>- Filip</div> <div><br> </div> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Wed, Nov 6, 2019 at 5:15 PM Sara Stymne <<a href="mailto:sara.stymne@lingfil.uu.se" target="_blank">sara.stymne@lingfil.uu.se</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir="ltr"> <div id="m_-3348210031780987899gmail-m_8741135732647666799divtagdefaultwrapper" style="font-size:12pt;font-family:Calibri,Helvetica,sans-serif" dir="ltr"> <p>Hi everyone,</p> <p><br> </p> <p>It is time to finalize the parsing deliverable for NLPL. We should make a plan for this. Our main idea is to migrate to Saga (and possibly Puhti) and mainly update the existing tools. Feel free to add any other relevant person to this conversation.</p> <p><br> </p> <p>Jörg, you are not really involved. I just wanted to ask you if you plan to keep UD-pipe installed as in previous years? Or if we should consider doing that instead?</p> <p><br> </p> <p>Filip, do you have any plans for parsing? Maybe you can package your parser from CoNLL'18, and/or your cool FinBERT+Udify parser? Since they have really good results.</p> <p><br> </p> <p>Stephan, will you take care of the semantic parsers and data again? And if I understood correctly, you also installed some baseline parsers last year. Is that something you plan to do again on Saga?</p> <p><br> </p> <p>We plan to update our UUparser installation, and also add models for the Nordic languages. We will install some other state-of-the-art parser. Maybe Udify. And also update the data and tutorial. Then it depends a bit on your plans, if we also will install some more parsers.</p> <p><br> </p> <p>Also, let me know if you have any other plans or ideas concerning the parsing part of NLPL!</p> <p><br> </p> <p>Best,</p> <p>Sara<br> </p> <p><br> </p> </div> <u></u><br> <br> <br> <br> <br> <br> <br> <br> När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: <a href="http://www.uu.se/om-uu/dataskydd-personuppgifter/" target="_blank">http://www.uu.se/om-uu/dataskydd-personuppgifter/</a> <br> <br> E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: <a href="http://www.uu.se/en/about-uu/data-protection-policy" target="_blank">http://www.uu.se/en/about-uu/data-protection-policy</a> </div> </blockquote> </div> </div> </blockquote> </div> <br> </div> </blockquote> </div> </div> </blockquote> </div> <br> </body> </html>