SURVEY:SUMMARY:BUILD_DIFFICULTY[not_applicable, reasonable_effort, code_problematic or string] reasonable_effort
SURVEY:SUMMARY:CLASSIFICATION[practical,theoretical,hardware] practical
SURVEY:SUMMARY:CORRECT_CODE_LOCATION[string]
SURVEY:SUMMARY:PUBLISHED_CODE[not_applicable, yes, no] yes
SURVEY:SUMMARY:SAME_VERSION[not_applicable, yes, no_but_available, no_and_not_available] yes
SURVEY:SUMMARY:STUDY_FOUND_CORRECT_CODE[not_applicable, yes, no] yes
SURVEY:AUTHOR1:BUILD_COMMENT[string] We were surprised that the second group did not know how to invoke a JVM from the unix command line. Note that rvm is built in the dist directory (the jikesrvm.org website makes all this clear).
Really, our work is only useful for researchers working with jikesrvm, btrace etc
SURVEY:AUTHOR1:BUILD_DIFFICULTY[not_applicable, reasonable_effort, code_problematic or string] reasonable_effort
SURVEY:AUTHOR1:BUILD_DIFFICULTY_COMMENT[string] However, this assumes you have experience of using mercurial to obtain the right version of jikesrvm, and of building jikesrvm. We provided a script to facilitate this. All the problems your initial student report are related to jikesrvm not our code.
SURVEY:AUTHOR1:CLASSIFICATION[practical,theoretical,hardware] practical
SURVEY:AUTHOR1:CLASSIFICATION_COMMENT[string]
SURVEY:AUTHOR1:CORRECT_CODE_LOCATION[string]
SURVEY:AUTHOR1:PUBLIC_COMMENT[string] Our work is useful for researchers working with jikesrvm, btrace etc. Researchers need to understand how to build/use these tools before they look at our work. We strongly suggest that your study applies at least the same standards of evaluation as those used by the ECOOP Artifact Evaluation process.
SURVEY:AUTHOR1:PUBLISHED_CODE[not_applicable, yes, no] yes
SURVEY:AUTHOR1:SAME_VERSION[not_applicable, yes, no_but_available, no_and_not_available] yes
SURVEY:AUTHOR1:SAME_VERSION_COMMENT[string]
SURVEY:AUTHOR1:STUDY_FOUND_CORRECT_CODE[not_applicable, yes, no] yes