In Europe the effort to build an open ocean seafloor observation infrastructure has been supported by the EC (European Commission) first through ESONET -NoE (European Seas Observatory NETwork -Network of Excellence), aimed at gathering together the community interested in multidisciplinary ocean observatories and more recently with the EMSO - PP project (European Multidisciplinary Seafloor Observatory -Preparatory Phase) aimed at establishing the legal entity charged of the construction and management of the EMSO infrastructure. The future directions on platforms' development need to address a number of limitations highlighted through the experience acquired over a decade of operation (also see Rountree et al., 2020): i) The operational cost is high, partly because underwater vehicles are required for maintenance operation to place the sensor with precision and perform underwater connection ii) the time between the maintenance operations is limited due to requirement for sensor calibration and, in case of wireless system, for energy pack and data storage replacement iii) the spatial coverage is limited to the close surrounding of the seabed station iv) new regulation will urge for new deployment processes with low environmental footprint v) a larger number and variety of sensors are fundamental for multidisciplinary approaches and the amount of energy and volume of data storage needed keeps increasing. These platforms can be cabled with power and data transmission ensured from the shore -but unchangeable location strongly constrains the cable route and price -, or wireless with battery and data storage capabilities dimensioned according to the duration of the foreseen deployment on board the seabed station (Matabos et al., 2016). Platforms that integrate ocean sensors and operate over a long time at sea can be fixed, e.g., surface buoys, moorings and landers, or mobile such as Argo floats, crawlers, surface vehicles, gliders and Autonomous Underwater Vehicles (AUV) (Aguzzi et al., 2019 Rountree et al., 2020). How do I get codeRunner in VSCode to recognize the file that im currently in, in this case dbhelper.py is the current working directory The reason I ask is because i created a Database class using postgres to help me with some personal research and wheneever i use dbhelper in different folders, its not recognizing the config.ini file I have in.

Coderunner cw