Switch branches/tags
Nothing to show
Commits on Feb 3, 2009
  1. Updated substruct service to accept GET or POST. If POST is specified…

    rajarshi committed Feb 3, 2009
    … then it accepts two form elements called query (a SMARTS pattern string) and target (a comma separate string of one or more SMILES). Return is a plain/text doc with N rows for N input SMILES, each row being true, false or fail if the pattern matched the SMILES, didn't match or failed to parse respectively
Commits on Jan 20, 2009
Commits on Jan 17, 2009
Commits on Jan 14, 2009
  1. Added sol models to the repo, to go with the current code. Updated di…

    rajarshi committed Jan 14, 2009
    …spatch to actually get the prediction
  2. Revert "Updated to recognize the fact that the descriptor service req…

    rajarshi committed Jan 14, 2009
    …uires base 64 encoded smiles"
    This reverts commit c7e6337.
Commits on Jan 13, 2009
  1. Updated README

    rajarshi committed Jan 13, 2009
  2. Removed the predictors script. Added a dispath module that allows us …

    rajarshi committed Jan 13, 2009
    …to get predictions from arbitrary models. Added example manifest file -allows us to serialize model details. It's the first version, so expect changes to manifast schema
  3. updated predict service to employ rpy2. Also added the start of a REA…

    rajarshi committed Jan 13, 2009
    …DME describing the services
Commits on Jan 12, 2009
Commits on Jan 11, 2009
  1. Updated descriptor service to only take base64 encoded smiles, since …

    rajarshi committed Jan 11, 2009
    …it simplified the code significantly. Looks a bit uglier though
Commits on Jan 7, 2009
  1. Updated to provide a plain tetx listing of available descriptors if the

    rajarshi committed Jan 7, 2009
    client specifically sets the Accept heder to just text/plain
Commits on Jan 5, 2009
Commits on Jan 4, 2009
  1. Fix ed a bug so that output is generated according to the first

    rajarshi committed Jan 4, 2009
    matching content type request, rathr than carrying on through the loop
  2. Updated chemspace service to consider all supplied client content types.

    rajarshi committed Jan 4, 2009
    Rather than just looking at the first content type, we loop over all
    supplied content types and take the first one that matches the supported
    types. This allows clients to suggest preferred types and if not supported
    get some other type of return page
Commits on Jan 3, 2009