{"id":2107,"date":"2020-11-11T07:38:59","date_gmt":"2020-11-11T07:38:59","guid":{"rendered":"https:\/\/lexis-project.eu\/web\/?page_id=2107"},"modified":"2021-10-26T17:18:24","modified_gmt":"2021-10-26T17:18:24","slug":"technical-documentation","status":"publish","type":"page","link":"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/","title":{"rendered":"Technical Documentation"},"content":{"rendered":"\n<h2>WHAT DOES LEXIS PROVIDE FOR APPLICATION EXPERIMENTS?<\/h2>\n\n\n\n<h3 id=\"lexis-portal-visualisation\">LEXIS PORTAL &amp; VISUALISATION<\/h3>\n\n\n\n<h4 class=\"pl10\">Web&nbsp;portal<\/h4>\n\n\n\n<p class=\"pl10\">The LEXIS Portal will act as the main entry point\nto LEXIS for users who are not experienced working with the LEXIS technology\nstack. Participants in the Open Call will be the first external users of this\nportal. The LEXIS Portal will provide functionality to interact with data sets\n(view public data sets, upload\/download private data sets), request access to\nresources by creating new projects, use and run workflows on a mix of HPC and\nCloud technologies as well as viewing usage and accounting information pertaining\nto use of the system resources.<\/p>\n\n\n\n<p class=\"pl10\">As the LEXIS portal is still new, the LEXIS team\nmembers will work with the Open Call participants more closely to understand\nthe usage of the LEXIS Portal (resource request, dataset and workflow\nmanagement), taking feedback from the usage and user experience, ergonomy and,\nwhere possible, modifying the functionality of the LEXIS Portal as necessary.<\/p>\n\n\n\n<h4 class=\"pl10\">Visualisation<\/h4>\n\n\n\n<p class=\"pl10\">The 3D remote visualization consists in giving the\nability for the LEXIS user to smoothly interact with their 2D or 3D\nhigh-demanding graphical applications, with neither the need of acceleration\n(GPU) on their client host, nor the need to download large (to extremely large)\ndatasets to view them. With such model, the data to be viewed remains on the\ncloud \/ server side as well as the 3D rendering power (GPU devices).<\/p>\n\n\n\n<p class=\"pl10\">Remote visualization middle-ware is necessary to\nencode the 3D experience being rendered on the server side into a streaming\nsystem able to accept the mouse and keyboard inputs from the user, in a way\nthat the user cannot really perceive the difference.<\/p>\n\n\n\n<p class=\"pl10\">At last, the LEXIS portal will make this complex\nmechanism transparent for the user, provided that this middleware provides a\nRESTful application programming interface (REST API).<\/p>\n\n\n\n<p class=\"pl10\">Use cases requiring such technology have been clearly identified for at least two of the existing pilots (for 3D interactive CFD simulation post-processing interactive encoding of weather forecast images into 2D videos). These use cases will be modelled in the orchestrator and stored in the related forge so that they can be reused in other\/new projects.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 id=\"technical-resources\">TECHNICAL RESOURCES<\/h2>\n\n\n\n<p class=\"pl10\">Both at IT4I and at LRZ, large-scale HPC\ninfrastructures in the Petaflop range (with HEAppE front-end) and Cloud\ninfrastructures (IaaS OpenStack for running VMs) with together more than 3,000\nCPU cores are accessible.<\/p>\n\n\n\n<p class=\"pl10\">On the storage side, we provide &gt;200TB of storage altogether without large bureaucratic barriers. Besides this, our Burst-Buffer systems can be used as a very quick intermediate data store in the multi-TB range, based on SSDs and NVRAM.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 id=\"computing-resources\">COMPUTING RESOURCES<\/h2>\n\n\n\n<p class=\"pl10\">European computing resources of world class level\nare made available through the LEXIS Open Call. The intended usage within the\nOpen Call is an<em> experimental usage with the focus on testing the LEXIS\nplatform<\/em>&nbsp;in order to validate and optimise the platform\u2019s\nfunctionality. This means, that scientific production usage is<em> generally not\nin the scope<\/em>.<\/p>\n\n\n\n<p class=\"pl10\">The new pilots can request a usage of the LEXIS\nplatform within the following limits:<\/p>\n\n\n\n<ul class=\"pl30\"><li>Normalised\ncore hours &#8211; minimum:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100,000\ncore hours<\/li><li>Normalised\ncore hours &#8211; maximum:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1,000,000\ncore hours<\/li><\/ul>\n\n\n\n<p class=\"pl10\">A definition of Normalised core hours (normalisation factors which relate the \u201craw\u201d core hours to the normalised values on each computing facility within the LEXIS platform) will be published with the open call.&nbsp; This definition may be subject to minor adjustments in the course of the project.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h3>LRZ\ncompute&nbsp;cloud, LINUX cluster &amp; SuperMUC-NG<\/h3>\n\n\n\n<p class=\"pl10\">At LRZ, LEXIS Customers have the access to HPC and\nCloud-Computing systems (in shared usage mode with other users). The systems\nrelevant for LEXIS are: <\/p>\n\n\n\n<ul class=\"pl30\"><li>LRZ Linux\nCluster &#8211; about 1 PFlop\/s, different segments (predominantly Intel Haswell\nCPUs), SLURM scheduler, parallel jobs with up to 1,792 cores on largest\n(Haswell-CPU-based) segment<\/li><li>SuperMUC-NG\n&#8211; 26 PFlop\/s, Intel Skylake, SLURM scheduler, OmniPath, jobs can scale up to\n147,456 cores \u2014 access to machine via special proposal<\/li><li>DGX-1 &#8211;\n170 TFlop\/s (FP16 Peak), NVIDIA P100 GPUs x 8, NVLink<\/li><li>LRZ\nCompute Cloud &#8211; IaaS Cloud with &gt;3000 Intel Skylake cores (and a few GPUs)\nfor the user to dynamically start Virtual Machines (VMs). Typical VMs have 4 GB\nof RAM per CPU core and a disk space of 20 GB<\/li><\/ul>\n\n\n\n<p class=\"pl10\">For further documentation see: <\/p>\n\n\n\n<ul class=\"pl30\"><li><a href=\"https:\/\/doku.lrz.de\/display\/PUBLIC\/High+Performance+Computing\">https:\/\/doku.lrz.de\/display\/PUBLIC\/High+Performance+Computing<\/a>&nbsp;<\/li><li><a href=\"https:\/\/doku.lrz.de\/display\/PUBLIC\/Compute+Cloud\">https:\/\/doku.lrz.de\/display\/PUBLIC\/Compute+Cloud<\/a>&nbsp;<\/li><\/ul>\n\n\n\n<p><\/p>\n\n\n\n<h3 class=\"pl10\">IT4I\ninfrastructure &amp; HPC clusters<\/h3>\n\n\n\n<p class=\"pl10\">The operational infrastructure at IT4I is the\nfollowing:<\/p>\n\n\n\n<ul class=\"pl30\"><li>Barbora\nHPC cluster &#8211; 848 TFlop\/s, Intel Cascade Lake, NVIDIA V100, InfiniBand HDR, PBS\nscheduler<\/li><li>Salomon\nHPC cluster &#8211; 2011 TFlop\/s, Intel Haswell, Xeon Phi, InfiniBand QDR, PBS\nscheduler<\/li><li>DGX-2 &#8211;\n520 PFlop\/s (FP16), 130 TFlop\/s (FP64), NVIDIA V100 GPUs x 16, NVLink<\/li><li>Anselm HPC\ncluster (decommission in Q4 2020) &#8211; 94 TFlop\/s, Intel Sandy Bridge, InfiniBand\nQDR, PBS scheduler<\/li><\/ul>\n\n\n\n<p class=\"pl10\">For further documentation see: <\/p>\n\n\n\n<ul class=\"pl30\"><li><a href=\"https:\/\/docs.it4i.cz\/\">https:\/\/docs.it4i.cz<\/a>&nbsp;<\/li><\/ul>\n\n\n\n<p class=\"pl10\">Furthermore, IT4I has procured an experimental infrastructure which will be used to operate a small OpenStack Cloud which will be provided to the call applicants as a resource. <\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 id=\"teseo-smart-gateway\">TESEO SMART GATEWAY<\/h2>\n\n\n\n<p class=\"pl10\">The smart gateway is mainly composed of three\nparts: <\/p>\n\n\n\n<ul class=\"pl30\"><li>Data\nreceiving module,<\/li><li>Data\nelaboration,<\/li><li>Data\nsharing.<\/li><\/ul>\n\n\n\n<p class=\"pl10\">Data receiving modules, based on a wireless LoRa\nmodule and on a RS485 wired link, are able to collect the data from the\ndifferent sensor nodes in the network. The core of the data elaboration part is\nan STM32 CPU based on an ARM CORTEX M7, and the main operations are data\ncollection pre-processing and submission. The data sharing part is devoted to\nthe data parsing &amp; formatting and data upload to the cloud, this part\ncurrently can be done via 3 different ways:<\/p>\n\n\n\n<ul class=\"pl30\"><li>WiFi\nconnection,<\/li><li>LAN\nconnection,<\/li><li>Narrow\nband connection.<\/li><\/ul>\n\n\n\n<p class=\"pl10\">The smart gateway in LEXIS provides a platform able\nto collect and send the data to a central database for the use of LEXIS weather\nand climate pilot. For the Open call, the smart gateway can easily collect and\nsend the data as actually is doing for the weather and climate pilot where the\nsmart gateway is collecting several data as is temperature, humidity,&nbsp;\npressure, wind speed, wind direction and precipitation intensity; these data\nare pre-validated directly by the smart gateway and shared via TCP\/IP protocol\nto an external database which than can be exploited for further services.<\/p>\n\n\n\n<p class=\"pl10\">TESEO expects to broaden the LEXIS project know-how\nthanks to additional real users\u00b4 experience using the smart gateway, so hard\ndata from the field.<\/p>\n\n\n\n<p class=\"pl10\">When required by the selected Applicant, TESEO will make available up to 10 Smart Gateways for the Open Call.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2>DATASETS<\/h2>\n\n\n\n<p class=\"pl10\">The LEXIS platform supports both the concept of\npublic and private datasets, meaning that all datasets can be protected with\nauthentication and authorization mechanisms preventing from unwanted access,\nsensitive data exposure or data leakage. <\/p>\n\n\n\n<p class=\"pl10\">As a matter of fact, the datasets can also be\nshared by LEXIS users or made publicly available on the LEXIS platform.<\/p>\n\n\n\n<p class=\"pl10\">It is worth mentioning that results are considered\nas regular datasets and follow the same rules to ensure both use case:<\/p>\n\n\n\n<ul class=\"pl30\"><li>Privacy of the results <\/li><li>Easy sharing results<\/li><\/ul>\n\n\n\n<p class=\"pl10\">The LEXIS Team will support the Open-Call\napplicants with the efficient use of external datasets they need as an input\nfor their scientific and industrial workflows. Such datasets, including\ndatasets not yet mentioned in the Pilots, will be made available in the DDI (or,\nif agreed on, also in the WCDA). Ideally, to this purpose, EUDAT staging\n(B2STAGE), synchronisation and federation (B2SAFE) mechanisms will be used. <\/p>\n\n\n\n<p class=\"pl10\">In addition, suitable datasets already available on\nEUDAT systems can be found via the B2FIND portal. The user can then upload\nthese datasets to the DDI using the appropriate APIs.<\/p>\n\n\n\n<p class=\"pl10\">Once in the DDI, data are subject to the convenient\nstaging mechanisms (DDI Staging API) within the orchestrated LEXIS workflows.\nAn overview of them is provided within the LEXIS Portal.<\/p>\n\n\n\n<p class=\"pl10\">As far as possible, applicants within the Open Call are expected to communicate their demands for external datasets at application time.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 id=\"data-management\">DATA MANAGEMENT &amp; PUBLICATION OF RESULTS<\/h2>\n\n\n\n<p class=\"pl10\">The LEXIS DDI (and, as far as agreed on, the WCDA)\ncan be used to store input, intermediate and output data of a new Pilot. A\nregular storage quota of 5 TB for persistent storage of a project is proposed,\nwhile up to 20 TB can be provided on negotiation (depending on availability).\nWe note that the HPC systems in LEXIS are equipped with temporary SCRATCH\nstorage in the range of 100s of TB per user, which can be used according to the\nregulations for the respective HPC system. Each project shall indicate expected\nstorage volumes for input, output, and intermediate data in their application\n(response to the Open Call).<\/p>\n\n\n\n<p class=\"pl10\">The data flow within the workflows, i.e. the\nprovisioning of input data and the de-provisioning, copying or archiving of\noutput data, is to be implemented via calls to the DDI APIs (mostly the staging\nHTTP-REST API) and the WCDA, which are normally receiving their calls directly\nfrom LEXIS workflow management.<\/p>\n\n\n\n<p class=\"pl10\">Once output data is archived within the DDI or the\nWCDA, the Data Management Approach of LEXIS includes the possibility to assign\npersistent identifiers (B2HANDLE PIDs, DOIs) as far as interesting and\nfeasible. This requires an obligatory provision of basic metadata (oriented\nmostly at the DataCite\/Dublin Core standards) which may be enforced already at\nearly stages of workflow definition. Clearly, the user having to do this is\nprovided support by the LEXIS team.<\/p>\n\n\n\n<p class=\"pl10\">Via the connection to EUDAT and its intrinsic\ngeographically-distributed nature, the DDI is able to offer redundant storage,\nand data find-ability via the EUDAT Collaborative Data Infrastructure (B2FIND)\n&#8211; if the user would like his data to be public.<\/p>\n\n\n\n<p class=\"pl10\">All the datasets (meaning input data, results, etc..) are handled from data lifecycle perspective, meaning for instance that all intermediate results are properly deleted when actively required or not being used anymore. Any LEXIS user has full control of its datasets during its lifecycle. In case some datasets are shared among LEXIS users by replication, then the replicated datasets is considered as uniq entity and has its own lifecycle and security policy.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 id=\"specific-workflows\">SPECIFIC WORKFLOWS<\/h2>\n\n\n\n<p class=\"pl10\">The LEXIS orchestration service will enable the\nmanagement of complex workflows represented by Directed acyclic graph,\nincluding:<\/p>\n\n\n\n<ul class=\"pl30\"><li>Cross\ncomputing between distributed HPC and Cloud infrastructures (hybrid workflow),<\/li><li>Urgent\ncomputing-oriented workflows,<\/li><li>Failover\nenabled workflows,<\/li><li>Data aware\nworkflows (including DDI operations).<\/li><\/ul>\n\n\n\n<p class=\"pl10\">A catalogue of workflows templates based on the\nLEXIS Pilots will be made available. It provides examples of typical workflows\naddressed by the project. The intent is that Open call participants will be\nable to directly use or customize these workflows to implement their use\ncases.&nbsp;<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" width=\"677\" height=\"162\" src=\"https:\/\/lexis-project.eu\/web\/wp-content\/uploads\/2020\/11\/technicalDocumentation.jpg\" alt=\"\" class=\"wp-image-2109\" srcset=\"https:\/\/lexis-project.eu\/web\/wp-content\/uploads\/2020\/11\/technicalDocumentation.jpg 677w, https:\/\/lexis-project.eu\/web\/wp-content\/uploads\/2020\/11\/technicalDocumentation-300x72.jpg 300w\" sizes=\"(max-width: 677px) 100vw, 677px\" \/><figcaption> Figure 1 Workflow example in Alien4Cloud UI <\/figcaption><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<h2>Security &amp; Confidentiality<\/h2>\n\n\n\n<p class=\"pl10\">While building the LEXIS Platform, the following\nconcerns were the main drivers for taking into account security very seriously\nsince the co-design:<\/p>\n\n\n\n<ul class=\"pl30\"><li>Data security during data life-cycle including authenticated and authorized access and public access as well. This results in the fact that all Data (input datasets and output results) can be private or not necessarily public: LEXIS platform is able to handle \u201csensitive data\u201d from customers and ensure end to end \u201cData Security\u201d (in-transit),<\/li><li>All source code (mainly algorithm) are following the main data security concept as they can be private or public: LEXIS platform allows to protect customer IP, by following Data Protection principles to protect source code of algorithm.<\/li><\/ul>\n\n\n\n<p class=\"pl10\">The LEXIS Platform has been built following best\npractice in the modern industry such as:<\/p>\n\n\n\n<ul class=\"pl30\"><li>Security by Design,<\/li><li>Zero trust model<\/li><li>Principles of least privileges<\/li><li>Defense in Depth<\/li><li>Separation of duties<\/li><li>Attack surface minimization, Keeping security simple and ensuring secure defaults.<\/li><\/ul>\n\n\n\n<p><\/p>\n\n\n\n<h2>SPECIFIC WORKFLOWS<\/h2>\n\n\n\n<h3>BASED ON PILOT FOR AERONAUTICS<\/h3>\n\n\n\n<p class=\"pl10\"><strong>Datasets<\/strong><\/p>\n\n\n\n<p class=\"pl10\">Because the software suite used within the\nAeronautics pilot is either proprietary or commercial this software could not\nbe used within the Open Call. For this reason, we prepared publicly\navailable&nbsp;dataset for Computational Fluid Dynamic (CFD) simulation\nexploiting LEXIS technologies which will leverage on open-source CFD code. This\ndata set will demonstrate the huge potential of LEXIS platform for CFD\nsimulations and since the intention of the Open Call is to target a broad\ncommunity, the provided data set has been prepared by using widely used\nopen-source CFD code OpenFOAM.&nbsp;This will allow users in Open Call to test\nprepared workflows and LEXIS technologies for their own applications. <\/p>\n\n\n\n<p class=\"pl10\">The test case provided in OpenFOAM format is the\nwell-known benchmark of T106C turbine profile tested on a&nbsp;linear cascade\nexperimental rig. Provided dataset contains not only geometrical description of\nthe blade in term of the coordinates, but inlet boundary conditions such as\ntotal pressure, temperature and flow angle, outlet boundary conditions such as\nstatic pressure but also all necessary OpenFOAM files.&nbsp;<\/p>\n\n\n\n<p class=\"pl10\">By providing OpenFOAM files, this dataset is ready-to-run on the LEXIS platform which makes it easy for user to get familiar with the LEXIS technologies and as such use easily the LEXIS platform test bed for CFD simulations.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2>SPECIFIC WORKFLOWS<\/h2>\n\n\n\n<h3>BASED ON PILOT FOR EARTHQUAKE &amp; TSUNAMI<\/h3>\n\n\n\n<p class=\"pl10\"><strong>Datasets<\/strong><\/p>\n\n\n\n<p class=\"pl10\">The earthquake and tsunami datasets will be\nprepared around the three scenarios planned for the evaluation of the pilot,\nthat is (i) the Padang earthquake and tsunami fictional event,&nbsp; (ii) the\nChile 2015 earthquake and tsunami and (iii) the Nepal 2015 earthquake events.\nEach dataset will include meshes for the tsunami simulations, the parameters\nfor the event (a QuakeML description file) and the exposure dataset subset, at\na pre-defined resolution. The data will be in the formats used by the various\ntools of the pilot workflow, that is mesh elements and nodes for TsunAWI, and\nOpenStreetMap subsets for the exposure dataset.<\/p>\n\n\n\n<p class=\"pl10\">A specific OpenStreetMap-based dataset and update set will be made available, to allow external participants to bench the update process of OpenBuildingMap.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2>SPECIFIC WORKFLOWS<\/h2>\n\n\n\n<h3>BASED ON PILOT FOR WEATHER &amp; CLIMATE<\/h3>\n\n\n\n<p class=\"pl10\"><strong>Datasets<\/strong><\/p>\n\n\n\n<h4 class=\"pl10\">Weather&nbsp;and&nbsp;climate&nbsp;pilot<\/h4>\n\n\n\n<p class=\"pl10\">A large portion of the data relevant to the weather\nand climate pilot is proprietary model output, used at an intermediate stage of\nthe pilot workflows, or third-party observations (e.g. Italian Civil Protection\nradar and weather stations observational data, Weather Underground personal\nweather stations) used as inputs, which cannot be shared publicly.<\/p>\n\n\n\n<p class=\"pl10\">However, the weather and climate pilot will make\nthe outcomes of its workflows publicly available where possible. This includes\nin particular the meteorological model WRF, Continuum hydrological model,\nRISICO forest fire risk model, ERDS model results, and NUM urban model\nresults.&nbsp; <\/p>\n\n\n\n<p class=\"pl10\">These results will be available for selected case\nstudies in Italy and France over selected periods. The modelling output will be\nmainly provided in NETCDF format. Furthermore, the main modelling tasks of the\nWeather and Climate pilot will adopt ad hoc virtualization techniques based on\ndockers and virtual machines. <\/p>\n\n\n\n<p class=\"pl10\">These virtualization approaches will allow the formulation of simplified modelling workflows to be demonstrated to&nbsp; external users to get familiar with the LEXIS technologies and to address possible approaches (portal, GUIs etc) to make easier for external actors the formulation of Weather and Climate experiments.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h4 class=\"pl10\">Urban&nbsp;air-quality&nbsp;dataset<\/h4>\n\n\n\n<p class=\"pl10\">In the framework of the weather and climate pilot,\nurban air-quality simulations over the whole Paris are produced for a set of\nspecific dates (year 2018). Note that the software used to produce this dataset\nis commercial and so cannot be used within the Open Call.<\/p>\n\n\n\n<p class=\"pl10\">This dataset consists of hourly time-series of 2D\nair-quality concentrations of NO2 and PM10 at ground level. The spatial\nresolution is irregular with 1&nbsp;m resolution close to main sources (road\nnetwork, industrial sources) up to 100m resolution far away. The output points\nare around 1,000,000 and cover a domain of about 28 km x 28 km over Paris. <\/p>\n\n\n\n<p class=\"pl10\">The format of the dataset is NetCDF, standardized\nfor the WCDA exchange API inside the LEXIS platform.<\/p>\n\n\n\n<p class=\"pl10\">The dataset is freely usable by the new partners of\nthe open call when it is an usage only inside the LEXIS platform for research\nor demonstration activities. No (direct or indirect) commercial use of this\ndataset is allowed.<\/p>\n\n\n\n<p class=\"pl10\">Execution of hydro-meteorological forecasting\nworkflows will be based on the following services:<\/p>\n\n\n\n<ul class=\"pl30\"><li>WRF model will be executed on HPC systems (LRZ and IT4I)<\/li><li>Containers and virtual machines will be executed on cloud computing<\/li><li>Workflows will be executed by the LEXIS Orchestration System based on TOSCA technology<\/li><\/ul>\n\n\n\n<p><\/p>\n\n\n\n<h4 class=\"pl10\">SPECIFIC WORKFLOWS for WEATHER &amp; CLIMATE <\/h4>\n\n\n\n<p class=\"pl10\">Two categories of workflows are envisaged:<\/p>\n\n\n\n<ol class=\"pl30\"><li>Exploiting pre-existing workflows to be used over different dates and areas<\/li><li>Exploiting WRF simulations, including data assimilation, and passing the results to external models to be executed on external premises <\/li><\/ol>\n","protected":false},"excerpt":{"rendered":"<p>WHAT DOES LEXIS PROVIDE FOR APPLICATION EXPERIMENTS? LEXIS PORTAL &amp; VISUALISATION Web&nbsp;portal The LEXIS Portal will act as the main entry point to LEXIS for users who are not experienced working with the LEXIS technology stack. Participants in the Open Call will be the first external users of this portal. The LEXIS Portal will provide [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1691,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v16.6.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\r\n<title>Technical Documentation - LEXIS project \/ LEXIS Platform<\/title>\r\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\r\n<link rel=\"canonical\" href=\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_GB\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Technical Documentation - LEXIS project \/ LEXIS Platform\" \/>\r\n<meta property=\"og:description\" content=\"WHAT DOES LEXIS PROVIDE FOR APPLICATION EXPERIMENTS? LEXIS PORTAL &amp; VISUALISATION Web&nbsp;portal The LEXIS Portal will act as the main entry point to LEXIS for users who are not experienced working with the LEXIS technology stack. Participants in the Open Call will be the first external users of this portal. The LEXIS Portal will provide [&hellip;]\" \/>\r\n<meta property=\"og:url\" content=\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/\" \/>\r\n<meta property=\"og:site_name\" content=\"LEXIS project \/ LEXIS Platform\" \/>\r\n<meta property=\"article:modified_time\" content=\"2021-10-26T17:18:24+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/lexis-project.eu\/web\/wp-content\/uploads\/2020\/11\/technicalDocumentation.jpg\" \/>\r\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\r\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"12 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/lexis-project.eu\/web\/#website\",\"url\":\"https:\/\/lexis-project.eu\/web\/\",\"name\":\"LEXIS project \/ LEXIS Platform\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/lexis-project.eu\/web\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/lexis-project.eu\/web\/wp-content\/uploads\/2020\/11\/technicalDocumentation.jpg\",\"contentUrl\":\"https:\/\/lexis-project.eu\/web\/wp-content\/uploads\/2020\/11\/technicalDocumentation.jpg\",\"width\":677,\"height\":162},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/#webpage\",\"url\":\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/\",\"name\":\"Technical Documentation - LEXIS project \/ LEXIS Platform\",\"isPartOf\":{\"@id\":\"https:\/\/lexis-project.eu\/web\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/#primaryimage\"},\"datePublished\":\"2020-11-11T07:38:59+00:00\",\"dateModified\":\"2021-10-26T17:18:24+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/lexis-project.eu\/web\/open-call\/technical-documentation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/lexis-project.eu\/web\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Introduction\",\"item\":\"https:\/\/lexis-project.eu\/web\/open-call\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Technical Documentation\"}]}]}<\/script>\r\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/pages\/2107"}],"collection":[{"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/comments?post=2107"}],"version-history":[{"count":36,"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/pages\/2107\/revisions"}],"predecessor-version":[{"id":2678,"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/pages\/2107\/revisions\/2678"}],"up":[{"embeddable":true,"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/pages\/1691"}],"wp:attachment":[{"href":"https:\/\/lexis-project.eu\/web\/wp-json\/wp\/v2\/media?parent=2107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}