Skip to content
This repository has been archived by the owner. It is now read-only.

/MTurkR Archived

GetAssignment issues #122

Closed
chriscastille6 opened this issue Jul 28, 2017 · 2 comments

Comments

Assignees
No one assigned
Labels
question wontfix
Projects
None yet
Milestone
No milestone
3 participants
@chriscastille6 @leeper @solstice
@chriscastille6
Copy link

commented Jul 28, 2017

I have a dataset of 121 people on Mturk for a particular HIT Id. When I use the following code:
a <- as.data.frame(GetAssignment(hit.type = [HIT ID Kept anonymous], return.all=TRUE))

My software locks up. I've traced this issue to using the "return.all=TRUE" function. If I switch that to "FALSE", then I can only pull 101 participants.

Any idea what could be the problem?

@leeper leeper added the question label Jul 29, 2017

@leeper

This comment has been minimized.

Sign in to view
Copy link
Member

commented Jul 29, 2017

What do you mean by "locks up"? Does it just take a long time or does R actually crash?
@solstice

This comment has been minimized.

Sign in to view
Copy link

commented Sep 13, 2017

I have a similar issue. When I run the command GetAssignments(hit.type = MYHITTYPEID, return.all = TRUE), I get this error repeatedly:

Request NA not valid for API request:
https://mechanicalturk.sandbox.amazonaws.com/?Service = AWSMechanicalTurkRequester
                                             &AWSAccessKeyId = REDACTED
                                             &SortDirection = Ascending 


Error (ServiceUnavailable):
  Service AWSMechanicalTurkRequester is currently unavailable. Please try again later

When I use the command without the return.all option, it returns all assignments related to the HIT type ID.

Also, when I use hit instead of hit.type, specifying the return.all = TRUE option also returns all assignments related to this specific HIT.

I am using this in the sandbox.

@leeper leeper added the wontfix label May 23, 2019

@leeper leeper closed this May 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.