search

thermofisherlsms / iapi

Instrument Application Programming Interface
MIT License
44 stars 17 forks source link

q-exactive support #11

Closed trishorts closed 1 year ago

trishorts commented 6 years ago

what is the status of this?

dbaileychess commented 6 years ago

We are looking into possible solutions of hosting the QE IAPI either in this repo or in its own. We have not finalized that decision yet, but I will keep this issue updated on those developments.

trishorts commented 6 years ago

thanks Derek. really looking forward to this.

tobiasko commented 6 years ago

Hi Derek,

following your ASMS2018 talk entitled:

"iAPI Development and XML Modification Overview: Thermo Scientific™ Tribrid™ and Exactive™ MS Series"

What is the current situation? Is there a separate iAPI for FUSION and Exactive platforms? Or is this repo now the main entry point for both systems? The current situation is pretty confusing.

Greetings, Tobi

dbaileychess commented 6 years ago

Tobi,

There is a functionally equivalent, binary-incompatible, version of the iAPI for the Fusion-series instruments. Both APIs are now hosted in this repo. We kept the two APIs in one repo since they do share so much in common that a shared issue-tracker and documentation made sense. Directories are split between Exactive-Series and Tribrid-Series files.

I will be adding more documentation in the upcoming weeks to help clarify the distinction. Please let me know of any specifics on the confusion and I will attempt to address them.

tobiasko commented 6 years ago

Hi Derek,

the mayor point of confusion is currently the licence agreement. There is one agreement for all platforms?

Greetings, Tobi

tobiasko commented 6 years ago

Hi Derek,

which Tune version is needed on the Exactive platforms?

Greetings, Tobi

jesse-canterbury commented 1 year ago

Closing this as obsolete. If there is still a need to address anything here, feel free to submit a new issue with updated information.