erwinhaasnoot / qrteparser-webservice Goto Github PK

Hello!

I am having issues running my data using the parser python file. I tried running this with a mac and a pc and it didn't work on either device. My friend who previously processed her data file using the parser ran the same file again and got a similar error message. I have pasted the error message below. I get this error message for every single participant. If you have any insight I would greatly appreciate it, thanks!

[/Users/jessicashropshire1/SocialVisionPsychTools/qrteparser-webservice/qrte_parser_python/qrtemarkupnode.py:346] [ERROR] [CODE:4][TAG:ERR_COLUMN_INVALID_JSON] Subject: R_Tc1yjGjaZiFrcqt, Data: , SubjectId: 42 - Column cache is not valid JSON. Likely that respondent quit the survey early. If this is not the case, please report immediately to [email protected], with the survey .qsf and the original data file.

The parser fails on my Qualtrics output file, which I think is because the 4 embedded data fields (QRTE_blockData, QRTE_idData, QRTE_exitQuestion and QRTE_columns) are empty. This happens with QRTE v17_jfe_fix and v15, and the experiment itself runs fine in both versions. Here's the parser error:

ERR_COLUMN_INVALID_JSON
UnboundLocalError: local variable 'exit_questions' referenced before assignment

The .qsf and an example Qualtrics output file can be found here.

Hi Erwin,

I just tried using the parser with Python 2.7 and Windows 7 64-bit, and I got the following error:

File "C:\Python27\qrteparser-webservice-master\parser.py", line 27, in
main(*sys.argv[1:])
File "C:\Python27\qrteparser-webservice-master\parser.py", line 22, in main
QRTEParser.parse(file, outfile=file.split('.')[0]+'_out.csv',exit_q_unique = False)
File "C:\Python27\qrteparser-webservice-master\qrte_parser_python\qrteparser.py", line 20, in
parse parser._parse()
File "C:\Python27\qrteparser-webservice-master\qrte_parser_python\qrteparser.py", line 32, in
parse node.write_data(self.file, self.outfile)
File "C:\Python27\qrteparser-webservice-master\qrte_parser_python\qrtemarkupnode.py", line > 94, in write_data csvwriter.open(outfile)
File "C:\Python27\qrteparser-webservice-master\qrte_parser_python\qrtecsv.py", line 63, in open
cls.filehandler = gzip.open(file+'.gz','wt')
File "C:\Python27\lib\gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
File "C:\Python27\lib\gzip.py", line 94, in init
fileobj = self.myfileobj = builtin.open(filename, mode or 'rb')
ValueError: Invalid mode ('wtb')

The parser produced an output file containing some of the embedded data, but that's it. I googled the error and found this, which suggests that it's a Python version issue. This seems strange since I'm sure I've used the parser with 2.7 before without any issues, and you mention using 2.7 in the instructions here.

I then tried the parser in Python 3 and didn't get an error. The output file looks great except that there are additional blank rows between each row of data.

Any idea what's going on here? Am I doing something wrong? I can email you the files if you'd like them.

Thanks very much!
Becky

Hi Erwin,

I'm getting the following error when I try to use the parser on all data files from an experiment. I'm using Python 3.5.0 and Windows 7 64-bit.

[ERROR] [CODE:2][TAG:ERR_MISSING_INDEX_1] Subject: R_2qmTpwrdVd4bJXw, SubjectId: 1,
ExitQuestion: SRPracExit - Exit question with index 1 is missing. Either Subject did not go through
Indicated block, or wrong row indices are used in Loop & Merge spreadsheet for Trial block with
mentioned Exit Tag. Please fix.

Is this referring to a missing exit question in the embedded data field QRTE_exitQuestions? If so, I'm confused because I can see in the Qualtrics file that 'SRPracExit' is there, listed first.

I'm wondering if this error has anything to do with the fact that the formatting of the qualtrics files goes weird when they're opened with Excel because the number of characters in the QRTE_idData JSON is longer than the maximum that can be displayed in Excel. As a result, the leftover characters in QRTE_idData are moved to the next row, followed by the rest of the data (which is no longer under the appropriate column heading). However, this seems to be strictly a display issue specific to Excel, because the file looks normal when I open it in R, so maybe it's totally unrelated?

You can get an example file here.

Can you tell me why these files aren't parsing and if there's anything I can do?

Thanks,
Becky