Niranjan Posted February 16, 2022 Share Posted February 16, 2022 I Have an use case where I need to import non-time series data for performing some calculations in Seeq. Can someone help me how can I import the non-time series data using CSV or SDK? Link to comment Share on other sites More sharing options...
Seeq Team Sharlinda Salim Posted February 16, 2022 Seeq Team Share Posted February 16, 2022 Hi Niranjan, Can you please provide a bit more background on your use case and calculations for us to have a bit more insight. Thank you. Regards, Sharlinda Link to comment Share on other sites More sharing options...
Niranjan Posted February 16, 2022 Author Share Posted February 16, 2022 Thanks for responding, The use case is like below: We have LIMS (Laboratory Information Management System) data and PI data. PI Data will have timestamp in it and LIMS will have only the Sample Id's, components and their values. Example LIMS: Sample ID, User Sample Id, Component, Value S-11111, S-11111-PRODUCT, Component1, 0.5 S-11112, S-11112-PRODUCT, Component2, 5.5 S-11113, S-11113-PRODUCT, Component3, 58 Example PI: Reading Time, Tag, Value 02/16/2022 15:30:01, Tag1, 0.5 02/16/2022 15:30:02, Tag2, 1.5 02/16/2022 15:30:03, Tag3, 5 02/16/2022 15:30:04, Tag4, 105 In the above case, We use both data for some custom calculations and get the results & plot the graphs. So PI Data i can import to Seeq but not LIMS data as it does not have time stamp. Link to comment Share on other sites More sharing options...
Seeq Team Joe Reckamp Posted February 16, 2022 Seeq Team Share Posted February 16, 2022 Hi Niranjan, Data must have a timestamp in order for it to be possible to upload into Seeq. Usually for LIMS data, there is a timestamp that is either when the sample was taken (less common) or when the sample test was performed (more common). Even if that timestamp does not correspond in time to when the batch was being run, we can move that LIMS data back in time if there is some sort of identifier that tells it which batch or data it may belong to. However, it does need to have a timestamp in order to be uploaded into Seeq. Link to comment Share on other sites More sharing options...
Niranjan Posted February 16, 2022 Author Share Posted February 16, 2022 Thank you If I need to import the data then somehow I need to get the Date or need to prefix some static date like below right: Static Date, Sample ID, User Sample Id, Component, Value 02/16/2022 15:30:01, S-11111, S-11111-PRODUCT, Component1, 0.5 02/16/2022 15:30:01, S-11112, S-11112-PRODUCT, Component2, 5.5 02/16/2022 15:30:01, S-11113, S-11113-PRODUCT, Component3, 58 In this case, Is there a way to make Date, Sample ID & Component as unique? So that I will never have a duplicate values. Link to comment Share on other sites More sharing options...
Seeq Team Joe Reckamp Posted February 16, 2022 Seeq Team Share Posted February 16, 2022 Hi Niranjan, Just so you're aware, Seeq does not allow duplicate timestamps for signals if that's the way you way to import the data, but does allow duplicate timestamps for capsules if you import the data as a condition. It's often best to import this data as a condition anyways with each of the columns being a property on each capsule as all of the information is related and that retains those relationships between the various columns. I'm not sure what you are asking with the final part - you can choose what date you use for Seeq or use whatever might be in the database already. Are the Sample ID and Component already unique? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now