Function get_request_state does not exist

[ghost]

The function does not/no longer exists but is mentioned in the API reference, e.g., under the point count_regions. Since the corresponding section in the API docs lists only _get_requestdata and _listrequests, I assume there is a minor design glitch because - apparently - it is no longer possible to query DeepBlue for the current state of a request.

[felipealbrecht]

We are going to remove it from the documentation. Use the command info("request_id", user_key)

Peter Ebert wrote:

The function does not/no longer exists but is mentioned in the API reference, e.g., under the point count_regions. Since the corresponding section in the API docs lists only /get_request_data/ and /list_requests/, I assume there is a minor design glitch because - apparently - it is no longer possible to query DeepBlue for the current state of a request.

— Reply to this email directly or view it on GitHub https://github.com/MPIIComputationalEpigenetics/DeepBlue/issues/82.

[felipealbrecht]

Btw, where is written to use "get_request_state" ?

Peter Ebert wrote:

The function does not/no longer exists but is mentioned in the API reference, e.g., under the point count_regions. Since the corresponding section in the API docs lists only /get_request_data/ and /list_requests/, I assume there is a minor design glitch because - apparently - it is no longer possible to query DeepBlue for the current state of a request.

— Reply to this email directly or view it on GitHub https://github.com/MPIIComputationalEpigenetics/DeepBlue/issues/82.

[felipealbrecht]

I found, is it in the tutorial http://deepblue.mpi-inf.mpg.de/tutorials/05-experiments.html ?

If yes, I am already fixing it.

Peter Ebert wrote:

The function does not/no longer exists but is mentioned in the API reference, e.g., under the point count_regions. Since the corresponding section in the API docs lists only /get_request_data/ and /list_requests/, I assume there is a minor design glitch because - apparently - it is no longer possible to query DeepBlue for the current state of a request.

— Reply to this email directly or view it on GitHub https://github.com/MPIIComputationalEpigenetics/DeepBlue/issues/82.

[ghost]

Well, as I wrote in my original ticket:

• but is mentioned in the API reference, e.g., under the point count_regions

I assume it's all over the place depending on when you decided a dedicated function was unnecessary.

[felipealbrecht]

Okay, thanks. I already fixed and committed the code. (but I will not put in the live server right now..) As well, I updated the tutorials and manual.

Peter Ebert wrote:

Well, as I wrote in my original ticket:

• but is mentioned in the API reference, e.g., under the point _countregions

I assume it's all over the place depending on when you decided a dedicated function was unnecessary.

— Reply to this email directly or view it on GitHub https://github.com/MPIIComputationalEpigenetics/DeepBlue/issues/82#issuecomment-149710528.