This is a .Net Core 1.1 service that provides a REST API to do data processing via MSDial.

How do I get set up?

git clone
  • Go to the MsdialRest folder and run the following commands:
cd msdialrest\src\msdialrest
dotnet restore
dotnet build
dotnet publish -c Release -o app [-r win7-x64] (the optional -r flag is to create an executable file)
  • Go to the app folder and run MsdialRest.exe
  • Alternatively you can run the application with
dotnet run

How to process data

The process is as follows:

Use the form to upload abf files, write a client of your own, or use curl:

curl -F files=@fileName.abf http://<serverUrl>/rest/upload

adding as many -F files=@... parameters as files that need to be uploaded; the 'files' name is required since it is what the server variable that holds the file data.

The response is a map (abf file name, schedule url) that can be used to schedule each particular file.


From this point on all the endpoints need an authorization token to be sent with the request as an Authorization header. This token is the main file to be deconvoluted, e.a.:

for a zipped Agilent file ( the authorization token will be test.d
for an abf file the autorization token will be the same filename

After the files are on the server calling the schedule url will start the deconvolution process (with default paramerters):

curl http://server/rest/deconvolution/schedule/<id>

To use custom parameters it is necessary to do a POST request to the same url but with a JSON body containing a Parameters object based on the following schema:


The response is a simple json obj:

  "message": "blah.abf was scheduled using parameters from <params file>", 

This is a blocking process right now but we can async it later; so the "status" endpoint is useless (the process already finished when you see the response).

Using the url in 'status' returns information about a file:

curl http://server/rest/deconvolution/status/<id>

The response looks like:


To download the results use the url on 'path'

Who do I talk to?