Hi everyone,
I am wondering: what is the best way to propose code changes to the openBIS codebase?
The gitlab project does not allow opening issues or direct collaboration like Merge Requests (for me).
kind regard,
Cagtay
Hi everyone,
I am wondering: what is the best way to propose code changes to the openBIS codebase?
The gitlab project does not allow opening issues or direct collaboration like Merge Requests (for me).
kind regard,
Cagtay
Hi Cagtay,
At this point to collaborate we would need to provide you with an account to open merge requests.
On the future we plan to have a copy of the repository on github to facilitate collaboration.
Might share what are you working on?
Hi Juan,
thanks for getting back so quickly. Good news about possible Github collab in the future.
For now I looked into supporting millisecond timestamp precision (basically following up on Property Data Types - #3 by CagtayFabry )
I started working on an initial review and implementation plan (with LLM assistance obviously, I tried to trace the main steps through the codebase but you will have much deeper knowledge obviously)
The inital assesment is that millisecond precision should be feasible with minimal targeted changes. Happy to discuss this with you via mail or similar, I will prepare a local test for demonstration soon.
What is your use case?
This is supported on the database so I guess you are proposing changes to the way we show it on the UI?
Some of our experiments are recorded with high precision in a real time context.
I want to preseve that precision when setting START_DATE / END_DATE or similar (e.g. for high frequency recordings and synchronized videos). Some of our workflows rely on the order in which experiments where started which can get difficult with rounding.
Currently timestamps get rounded to s in multiple places (e.g. directly in pybis which I am using mostly)
But as far as I found the backend fully supports ms precision as you mentioned, it just needs to be enabled and supported in the UI.