Update project's content with time domain formulation of virtual sensing and...

Update project's content with time domain formulation of virtual sensing and updated roadmap section in README.md

README.md

-# IN-NOVA
+C# IN-NOVA
 This repository holds the open-access codebase used within the [IN-NOVA](https://in-nova-horizon.eu/) project. The codebase is divided into various sections, each relevant to a different topic/problem. The sections will be updated and more sections will be added on an as-needed basis, since the purpose of the project is not to create a software library to tackle the scientific problems.
 
 The codebase under each section may or may not include code implementations in different languages but no plan exists to port each implementation in all available programming languages. More information about the codebase, the available implementations and topics/fields can be found in the [Documentation](https://gitlab.com/in-nova/in-nova/-/tree/main/Documentation/latex?ref_type=heads) of the project and its [Wiki](https://gitlab.com/in-nova/in-nova/-/wikis/home).
@@ -17,6 +17,8 @@ The current structure of the codebase is shown below. More information can be fo
     - Frequency domain
 - [Virtual Sensing](https://gitlab.com/in-nova/in-nova/-/tree/main/Virtual%20Sensing)
   - Remote Microphone Technique
+    - Frequency domain
+    - Time domain
 - [Optimisation](https://gitlab.com/in-nova/in-nova/-/tree/main/Optimisation/Memetic%20Algorithm)
   - Memetic Algorithm
 - [Signal Processing](https://gitlab.com/in-nova/in-nova/-/tree/main/Signal%20Processing)
@@ -34,7 +36,9 @@ If you find any bugs, other issues and/or inconsistencies you can [e-mail](mailt
 ## Roadmap
 The repository will be updated on an as-needed basis.
 
-At this stage, the repository is *under construction* and the main focus lies on uploading the available code, updating documentation and structuring the GitLab project to contain all information related to the codebase.
+Although the repository is not considered to be *under construction* anymore, there are significant gaps in its structure. At the moment, the main focus is placed on updating code with new features and bug fixes and documenting ideas and useful features for the future (mainly as issues).
+
+As a parallel slow-moving project, porting the codebase to [Julia](https://julialang.org/) has also started, aiming to provide full functionality in the future. Although Julia and MATLAB were designed to tackle similar (if not the same) problems, they are quite different. The facilities and intricacies of Julia dictate the need to dig deeper into the language in order to provide an efficient, maintainable and intuitive codebase that will parallel the current MATLAB implementation in functionality. More time must be spent in the design phase for the Julia implementations, which will, most probably, keep the progress to a slow pace. Although it is a long shot, the target is for the Julia codebase to reach the MATLAB implementation's state and then move forward in tandem.  
 
 ## Contributing
 If you would like to contribute to the project you could do that in various ways, as listed below: