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

CreateQualificationType error for .xml with multiple overview sections #117

Closed
darrellpenta opened this issue Jan 21, 2017 · 8 comments

Comments

Projects
None yet
2 participants
@darrellpenta
Copy link

commented Jan 21, 2017

Thank you, @leeper. MTurkR and MTurkRGUI are amazing packages.

Wondered if you might have any insight on an issue when trying to create qualifications with more than one overview section. The function (as below) works when qtest = qualitifcationstest1.xml and qanswer = answerkey1.xml. It also handles additional questions and answers without any issues.

qual_test <- 
      MTurkR::CreateQualificationType(
      name = "MyTest",
      description = MyDesription,
      test = qtest,
      answerkey = qanswer,
      retry.delay = 1,
      test.duration = 600,
      status = "Active",
      keywords = qkeyword)

However, if I add <Overview><Text>Overview 2</Text></Overview> along with an additional group of questions, I get:

> Error in rbind.data.frame(Overview = list(ElementNumber = 1L, Element = "Overview",
   :numbers of columns of arguments do not match

There doesn't appear to be any trouble using the same file when creating a qualification manually through the MTurk CLI.

Not sure whether this was previously addressed https://github.com/cloudyr/MTurkR/issues/8, or what the status might be.

Package info:
MTurkR * 0.7.11 2017-01-18
MTurkRGUI * 0.1.5 2017-01-18

System Info:
R version 3.3.2 (2016-10-31)
System x86_64, darwin13.4.0 (Mac Osx)

.

leeper added a commit that referenced this issue Jan 21, 2017

@leeper

This comment has been minimized.

Copy link
Member

commented Jan 21, 2017

I've just sent a patch that I will get around this. Want to try reinstalling MTurkR from GitHub and trying again?

@leeper leeper added the bug label Jan 21, 2017

@darrellpenta

This comment has been minimized.

Copy link
Author

commented Jan 21, 2017

Excellent! Thank you. I reinstalled from GitHub and this seems to have solved the issue. Can't express how much I appreciate your reply and your efforts in creating such a useful package.

@leeper

This comment has been minimized.

Copy link
Member

commented Jan 21, 2017

Excellent.

@darrellpenta

This comment has been minimized.

Copy link
Author

commented Feb 10, 2017

@leeper leeper reopened this Feb 10, 2017

@leeper

This comment has been minimized.

Copy link
Member

commented Feb 11, 2017

@darrellpenta Can you show the exact code that is generating that warning?

@darrellpenta

This comment has been minimized.

Copy link
Author

commented Feb 12, 2017

Hey @leeper

I've got an annotated R script (and everything else you'd need) to recreate the warnings. Please let me know if you didn't get the invite to the repository, and please let me know if there are any issues getting things to work.

@leeper

This comment has been minimized.

Copy link
Member

commented Feb 12, 2017

@darrellpenta Thanks. These can be safely ignored. It's an unfortunate consequences of how I've setup the use of ..., passing values to both RegisterHITType() and CreateHIT() inside the BulkCreateFromHITLayout() function.

If you set verbose = FALSE, these will go away entirely per code here.

I'll put it on my todo list to stop the title, description, reward, and duration arguments from getting passed to CreateHIT() here, thus eliminating the warning.

@darrellpenta

This comment has been minimized.

Copy link
Author

commented Feb 12, 2017

Thanks for the info, @leeper. In fact, I've been ignoring the warnings all along as the function works perfectly well!

@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.