|
7 | 7 |
|
8 | 8 | <div class="row"> |
9 | 9 | <div class="col"> |
| 10 | + |
10 | 11 | <h3>Current work</h3> |
11 | 12 | <p> |
12 | 13 | <ul> |
13 | 14 | <li> |
14 | 15 | <p> |
15 | | - <b>Integration of MLFLow for ML experiment tracking</b> |
| 16 | + <b>Metadata and FAIR improvements</b> |
16 | 17 | </p> |
17 | 18 | <p> |
18 | | - We will allow users of SciLifeLab Serve to launch their own instances of the platform <a |
19 | | - href="https://mlflow.org/">MLFlow</a> that allows to keep track of models and artifacts in machine learning |
20 | | - work. Users will be able to send data to their instance from anywhere where they are doing training or |
21 | | - analyses. |
| 19 | + We will be collecting additional information about applications and models published on SciLifeLab Serve |
| 20 | + (such as list of authors and source of funding). We will also be registering Digital Object Identifiers |
| 21 | + (DOIs) to allow tracking of metadata and citation of applications and models. |
22 | 22 | </p> |
23 | 23 | <p> |
24 | | - <i>Released Q1 2025</i> |
| 24 | + <i>Planned Q4 2025</i> |
25 | 25 | </p> |
26 | 26 | </li> |
27 | 27 | <li> |
28 | 28 | <p> |
29 | | - <b>Support for model deployment with GPUs</b> |
| 29 | + <b>Improved web accessibility of the website</b> |
30 | 30 | </p> |
31 | 31 | <p> |
32 | | - We will allow users to publish models with access to GPUs to run inferences. We will start with a few pilot |
33 | | - projects before making it widely available. Get in touch with us if you are interested in being a pilot |
34 | | - user. |
| 32 | + We will review and update our webpages to meet the |
| 33 | + <a href="https://www.w3.org/WAI/standards-guidelines/wcag/glance/" |
| 34 | + target="_blank" |
| 35 | + rel="noopener noreferrer"> |
| 36 | + Web Content Accessibility Guidelines (WCAG) 2.2 <span class="sr-only">(opens in a new tab)</span> |
| 37 | + </a> |
35 | 38 | </p> |
36 | 39 | <p> |
37 | | - <i>Planned Q2 2025</i> |
| 40 | + <i>Planned Q4 2025</i> |
38 | 41 | </p> |
39 | 42 | </li> |
40 | 43 | </ul> |
41 | 44 | </p> |
| 45 | + |
42 | 46 | <h3>Near-term work</h3> |
43 | 47 | <p> |
44 | 48 | <ul> |
45 | 49 | <li> |
46 | 50 | <p> |
47 | | - <b>Metadata and FAIR improvements</b> |
| 51 | + <b>Access to an API endpoint to interact with LLM(s)</b> |
48 | 52 | </p> |
49 | 53 | <p> |
50 | | - We will be collecting additional information about applications and models published on SciLifeLab Serve |
51 | | - (such as list of authors and source of funding). We will also be registering Digital Object Identifiers |
52 | | - (DOIs) to allow tracking of metadata and citation of applications and models. |
| 54 | + We will provide an API endpoint for application developers that will allow their apps to interact with one |
| 55 | + or more LLMs. The apps will then need to be made available through SciLifeLab Serve. |
53 | 56 | </p> |
54 | 57 | <p> |
55 | | - <i>Planned Q3 2025</i> |
| 58 | + <i>Planned Q1 2026</i> |
56 | 59 | </p> |
57 | 60 | </li> |
| 61 | + </ul> |
| 62 | + </p> |
| 63 | + |
| 64 | + <h3>Long-term work</h3> |
| 65 | + <p> |
| 66 | + <ul> |
58 | 67 | <li> |
59 | 68 | <p> |
60 | | - <b>Improved web accessibility of the website</b> |
| 69 | + <b>Improved model-serving functionality</b> |
61 | 70 | </p> |
62 | 71 | <p> |
63 | | - We will review and update our webpages to meet the Web Content Accessibility Guidelines (WCAG) 2.2. |
| 72 | + We will improve the user experience and useability of deploying and using machine learning models through SciLifeLab Serve. |
64 | 73 | </p> |
65 | 74 | <p> |
66 | | - <i>Planned Q3 2025</i> |
| 75 | + <i>Planned 2026</i> |
67 | 76 | </p> |
68 | 77 | </li> |
69 | 78 | <li> |
70 | 79 | <p> |
71 | | - <b>Access to an API endpoint to interact with LLM(s)</b> |
| 80 | + <b>LLM-empowered application creation</b> |
72 | 81 | </p> |
73 | 82 | <p> |
74 | | - We will provide an API endpoint for application developers that will allow their apps to interact with one |
75 | | - or more LLMs. The apps will then need to be made available through SciLifeLab Serve. |
| 83 | + We will integrate an interface allowing to build data science applications by interacting with an LLM |
| 84 | + through a chat interface. These applications can then be published on SciLifeLab Serve. |
76 | 85 | </p> |
77 | 86 | <p> |
78 | | - <i>Planned Q3 2025</i> |
| 87 | + <i>Planned 2026</i> |
79 | 88 | </p> |
80 | 89 | </li> |
81 | 90 | </ul> |
82 | 91 | </p> |
83 | | - <h3>Long-term work</h3> |
| 92 | + |
| 93 | + <h3>Past work</h3> |
84 | 94 | <p> |
85 | 95 | <ul> |
86 | 96 | <li> |
87 | 97 | <p> |
88 | | - <b>LLM-empowered application creation</b> |
| 98 | + <b>Integration of MLFLow for ML experiment tracking</b> |
89 | 99 | </p> |
90 | 100 | <p> |
91 | | - We will integrate an interface allowing to build data science applications by interacting with an LLM |
92 | | - through a chat interface. These applications can then be published on SciLifeLab Serve. |
| 101 | + We will allow users of SciLifeLab Serve to launch their own instances of the platform <a href="https://mlflow.org/" |
| 102 | + target="_blank" rel="noopener noreferrer"> MLflow <span class="sr-only">(opens in a new tab)</span> |
| 103 | + </a> that allows to keep track of models and artifacts in machine learning |
| 104 | + work. Users will be able to send data to their instance from anywhere where they are doing training or |
| 105 | + analyses. |
93 | 106 | </p> |
94 | 107 | <p> |
95 | | - <i>Planned Q4 2025</i> |
| 108 | + <i>Released Q1 2025</i> |
| 109 | + </p> |
| 110 | + </li> |
| 111 | + <li> |
| 112 | + <p> |
| 113 | + <b>Support for model deployment with GPUs</b> |
| 114 | + </p> |
| 115 | + <p> |
| 116 | + We will allow users to publish models with access to GPUs to run inferences. We will start with a few pilot |
| 117 | + projects before making it widely available. Get in touch with us if you are interested in being a pilot |
| 118 | + user. |
| 119 | + </p> |
| 120 | + <p> |
| 121 | + <i>Released Q2 2025</i> |
96 | 122 | </p> |
97 | 123 | </li> |
98 | 124 | </ul> |
|
0 commit comments