481
481
< h1 > Roadmap< a class ="headerlink " href ="#roadmap " title ="Link to this heading "> #</ a > </ h1 >
482
482
< section id ="future-milestones ">
483
483
< h2 > Future milestones< a class ="headerlink " href ="#future-milestones " title ="Link to this heading "> #</ a > </ h2 >
484
- < section id ="features ">
485
- < h3 > Features< a class ="headerlink " href ="#features " title ="Link to this heading "> #</ a > </ h3 >
484
+ < section id ="features-or-enhancements ">
485
+ < h3 > Features or enhancements < a class ="headerlink " href ="#features-or-enhancements " title ="Link to this heading "> #</ a > </ h3 >
486
486
< ul class ="simple ">
487
- < li > < p > Add a Jupyter kernel interface to DataLab :</ p >
487
+ < li > < p > Add support for data acquisition :</ p >
488
488
< ul >
489
- < li > < p > This would allow to use DataLab from other software, such as Jupyter
490
- notebooks, Spyder or Visual Studio Code</ p > </ li >
491
- < li > < p > This would also allow to share data between DataLab and other software
492
- (e.g. display DataLab numerical results in Jupyter notebooks or the other
493
- way around, display Jupyter results in DataLab, etc.)</ p > </ li >
489
+ < li > < p > It would be nice to be able to acquire data from various sources
490
+ (e.g. a camera, a digitizer, a spectrometer, etc.) directly from DataLab</ p > </ li >
491
+ < li > < p > This would allow to use DataLab as a data acquisition software, and to
492
+ process the acquired data immediately after</ p > </ li >
493
+ < li > < p > Although there is currently no design for this feature, it could be
494
+ implemented by creating a new plugin family, and by defining a common
495
+ API for data acquisition plugins</ p > </ li >
496
+ < li > < p > One of the possible technical solutions could be to rely on < a class ="reference external " href ="https://pymodaq.cnrs.fr/ "> PyMoDAQ</ a > ,
497
+ a Python package for data acquisition, which is already compatible with
498
+ various hardware devices - < em > how about a collaboration with the PyMoDAQ
499
+ developers?</ em > </ p > </ li >
500
+ </ ul >
501
+ </ li >
502
+ < li > < p > Create a DataLab math library:</ p >
503
+ < ul >
504
+ < li > < p > This library would be a Python package, and would contain all the
505
+ mathematical functions and algorithms used in DataLab:
506
+ - A low-level algorithms API operating on NumPy arrays
507
+ - The base non-GUI data model of DataLab (e.g. signals, images)
508
+ - A high-level computing API operating on DataLab objects (e.g. signals, images)</ p > </ li >
509
+ < li > < p > It would be used by DataLab itself, but could also be used by third-party software
510
+ (e.g. Jupyter notebooks, Spyder, Visual Studio Code, etc.)</ p > </ li >
511
+ < li > < p > Finally, this library would be a good way to share DataLab’s mathematical features
512
+ with the scientific community: a collection of algorithms and functions
513
+ that are well-tested, well-documented, and easy to use</ p > </ li >
514
+ < li > < p > < em > Note</ em > : it is already possible to use DataLab’s processing features from outside
515
+ DataLab by importing the < cite > cdl</ cite > Python package, but this package also contains
516
+ the GUI code, which is not always needed (e.g. when using DataLab from a Jupyter
517
+ notebook). The idea here is to create a new package that would contain only the
518
+ mathematical features of DataLab, without the GUI code.</ p > </ li >
494
519
</ ul >
495
520
</ li >
496
521
< li > < p > Create a Jupyter plugin for interactive data analysis with DataLab:</ p >
@@ -520,6 +545,19 @@ <h3>Features<a class="headerlink" href="#features" title="Link to this heading">
520
545
</ li >
521
546
< li > < p > Add support for time series (see
522
547
< a class ="reference external " href ="https://github.com/DataLab-Platform/DataLab/issues/27 "> Issue #27</ a > )</ p > </ li >
548
+ < li > < p > Add a Jupyter kernel interface to DataLab:</ p >
549
+ < ul >
550
+ < li > < p > This would allow to use DataLab from other software, such as Jupyter
551
+ notebooks, Spyder or Visual Studio Code</ p > </ li >
552
+ < li > < p > This would also allow to share data between DataLab and other software
553
+ (e.g. display DataLab numerical results in Jupyter notebooks or the other
554
+ way around, display Jupyter results in DataLab, etc.)</ p > </ li >
555
+ < li > < p > After a first and quick look, it seems that the Jupyter kernel interface
556
+ is not straightforward to implement, so that it may not be worth the effort
557
+ (the communication between DataLab and Jupyter is currently already possible
558
+ thanks to the remote control features)</ p > </ li >
559
+ </ ul >
560
+ </ li >
523
561
</ ul >
524
562
</ section >
525
563
< section id ="maintenance ">
@@ -538,8 +576,6 @@ <h3>Other tasks<a class="headerlink" href="#other-tasks" title="Link to this hea
538
576
< ul class ="simple ">
539
577
< li > < p > Create a DataLab plugin template (see
540
578
< a class ="reference external " href ="https://github.com/DataLab-Platform/DataLab/issues/26 "> Issue #26</ a > )</ p > </ li >
541
- < li > < p > Make tutorial videos: plugin system, remote control features, etc. (see
542
- < a class ="reference external " href ="https://github.com/DataLab-Platform/DataLab/issues/25 "> Issue #25</ a > )</ p > </ li >
543
579
</ ul >
544
580
</ section >
545
581
</ section >
@@ -666,7 +702,7 @@ <h3>DataLab 0.9<a class="headerlink" href="#datalab-0-9" title="Link to this hea
666
702
< nav class ="bd-toc-nav page-toc ">
667
703
< ul class ="visible nav section-nav flex-column ">
668
704
< li class ="toc-h2 nav-item toc-entry "> < a class ="reference internal nav-link " href ="#future-milestones "> Future milestones</ a > < ul class ="visible nav section-nav flex-column ">
669
- < li class ="toc-h3 nav-item toc-entry "> < a class ="reference internal nav-link " href ="#features "> Features</ a > </ li >
705
+ < li class ="toc-h3 nav-item toc-entry "> < a class ="reference internal nav-link " href ="#features-or-enhancements "> Features or enhancements </ a > </ li >
670
706
< li class ="toc-h3 nav-item toc-entry "> < a class ="reference internal nav-link " href ="#maintenance "> Maintenance</ a > </ li >
671
707
< li class ="toc-h3 nav-item toc-entry "> < a class ="reference internal nav-link " href ="#other-tasks "> Other tasks</ a > </ li >
672
708
</ ul >
0 commit comments