doc/homework/homework4.html - view

File: [LON-CAPA] / doc / homework / Attic / homework4.html
Revision 1.5: download - view: text, annotated - select for diffs
Sat May 19 01:04:55 2001 UTC (23 years, 1 month ago) by albertel
Branches: MAIN
CVS tags: version_0_4, stable_2002_spring, stable_2002_july, stable_2002_april, stable_2001_fall, STABLE, HEAD

*** empty log message ***

1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> 2: <html> 3: <head> 4: <title>LON-CAPA Homework System</title> 5: </head> 6: 7: <body> 8: <h1>LON-CAPA Homework System</h1> 9: 10: <h2>Tags</h2> 11: <ul> 12: Outtext is gone now 13: <li> 14: Output Tags 15: 16: 17: This set of tags control how and when data gets sent to the 18: student, it also provides hints to the data's markup and 19: when it should be autoconverted, and when it should be 20: ignored. All of these tags except <outtext> are 21: valid and parsed by &parsed() inside a <script>. 22: 23: 24: Additionaly any perl style variables are replaced with the 25: values of the variable in the problem namespace. 26: 27: <ul> 28: 29: <li> 30: <outtext> all data inside is assumed to be valid 31: html, the handler will attempt to autoconvert to the 32: output type. The only thing tags allowed inside are the 33: ones listed below. 34: </li> 35: <li> 36: <target> This tag specifies data that is not in 37: HTMl format inside an <outtext>. Takes a required 38: argument type and an optional argument 39: dest. type specifies a known valid 40: output target which is the format of the 41: data. dest specifies a list of possible output 42: targets that the data should be autoconverted for. The 43: type of the data is assumed to be a 44: dest. If the current target is not a 45: dest then the data is ignored. 46: </li> 47: 48: <li> 49: <tex> shorthand for <target type=``tex''> 50: dest is a valid argument. 51: </li> 52: 53: <li> 54: <ascii> shorthand for <target type=``ascii''> 55: dest is a valid argument. 56: </li> 57: 58: <li> 59: <web> shorthand for <target type=``web''> 60: dest is a valid argument. 61: </li> 62: 63: <li> 64: <mathml> shorthand for <target 65: type=``mathml''> dest is a valid argument, 66: mathml may be passed along unconverted in a web output 67: target. 68: </li> 69: 70: </ul> 71: </li> 72: 73: <li> 74: Form Elements: 75: 76: 77: This set of tags soley generate a representation of the proper 78: form element on the output device. Need to look at what should 79: be provided when an exam is wanted. 80: 81: <ul> 82: <li> 83: <radio> 84: 85: 86: web - provides a single button to check on and off, when 87: checked on all other radio buttons in the current 88: <answergroup> level will be set to off. 89: 90: 91: 92: tex - generates a circle before the data inside 93: 94: </li> 95: <li> 96: <list> 97: 98: web - provides a drop down box of all the possible options 99: 100: 101: tex - the list is displayed an students can select the 102: correct option 103: 104: </li> 105: <li> 106: <textline> 107: 108: web - a single line of reponse is provided to type into. 109: 110: 111: tex - a line is provided. 112: 113: </li> 114: <li> 115: <textarea> 116: 117: web - a textarea form is provided allowing multiples 118: lines of response 119: 120: 121: tex - a configureable number of lines is provided, 122: configured through the argument numlines, defaults to 10 123: 124: </li> 125: <li> 126: <check> 127: 128: web - either a checkbutton, or two radio buttons are provided 129: 130: 131: tex - a small box that can be checked is provided. 132: 133: </li> 134: <li> 135: <button> - Not sure this is useful 136: </li> 137: </ul> 138: </li> 139: <li> 140: Randomiztion 141: <ul> 142: <li> 143: <randomlist> this tag will cause the parser to 144: randomly select the order that it parses the next level of 145: tags, tags another leveldown will be done in order 146: though. Example: 147: <pre> 148: <randomlist> 149: <tag1> 150: <subtag1> 151: </subtag1> 152: <subtag2> 153: </subtag2> 154: </tag1> 155: <tag2> 156: <subtag1> 157: </subtag1> 158: <subtag2> 159: </subtag2> 160: </tag2> 161: </randomlist> 162: </pre> 163: In this example, <tag1> or <tag2> will be 164: done first, but <subtag1> will always happen before 165: <subtag2>. 166: </li> 167: <li> 168: <foil>, <showfoil/>, 169: <showrandomfoil/> These tags combine to allow the 170: user greater control over the exact placement of a 171: randomized problem text. a <foil> tag defines a 172: section of the problem that will appear in places a 173: <showfoil/> or <showrandomfoil/> mark. 174: Internally, the parser will make a pass over an entire 175: answer group and count the number of <foil>, 176: <showfoil/>, and <showrandomfoil/> tags 177: that are used it will then make another pass and parse all 178: of the <foil> storing the results of these parses, 179: while parsing for each <show*> tag it hits it will 180: send to the output device a foil, the <show*> it 181: hit was a <showfoil> and this was the nth 182: <show*> it hit, it will display the nth foil. For 183: each <showrandomfoil> it hits it will randomly pick 184: from the remaining foils a foil to send to the output. If 185: there are more <show*> tags than foils, the extra 186: <show*> will have nothing sent out. If there are 187: more <foil> tags, the extras won't appear. When 188: mixing <showfoil> and <showrandomfoil> the 189: result is undefined. 190: </li> 191: </ul> 192: </li> 193: <li> 194: Answer Section 195: <ul> 196: <li> 197: <*response> further documentation will be available 198: in the future. Roughly these will take a set of data from 199: the enclosed input structures, and one or more correct 200: answers and return a correct of incorrect result, it may 201: also suggest a consumption of a try, and may provide a 202: reason for the incorrectness. 203: 204: Required possible arguments: 205: 206: ID, if this isn't set it will be set during 207: the publication step. It is used to assign parameters names 208: in a way that can be tracked if an instructor modifies 209: things by hand. 210: 211: name optional, if set, it will be used by the 212: resource assembly tool when one is modfiying parameters. 213: </li> 214: <li> 215: <responseparam> can appear inside a <*response>, 216: they provided config options for the <*response> 217: 218: name specifies the parameter name, what are 219: possible values depends on the <*response> 220: 221: type specifies the possible values for this 222: type, possible arguments are: "option1|option2|option3" or 223: "numerictype,lownum-highnum" numeric type can be either int 224: or float 225: 226: default specifies the default value for this 227: parameter if the instructor doesn't specifiy it 228: 229: ID, if this isn't set it will be set during 230: the publication step. It is used to assign parameters names 231: in a way that can be tracked if an instructor modifies 232: things by hand. 233: </li> 234: </ul> 235: </li> 236: <li> 237: Problem Contruction 238: <ul> 239: <li> 240: <problem> highest level tag, tells the parser that 241: this is a problem file 242: 243: name optional, if set, it will be used by the 244: resource assembly tool when one is modfiying parameters. 245: </li> 246: <li> 247: part needs to get much of answergroups writeup 248: <part> a problem can consist of multiple parts, 249: each of these parts can be included or not included through 250: the construction of a page using the RAT, 251: 252: ID, if this isn't set it will be set during 253: the publication step. It is used to assign parameters names 254: in a way that can be tracked if an instructor modifies 255: things by hand. 256: 257: name optional, if set, it will be used by the 258: resource assembly tool when one is modfiying parameters. 259: </li> 260: <li> 261: <block> are section of the problem that can be 262: conditional, and provide visual grouping clues. The optional 263: arg condition is set to a perl snippet that 264: controls whether the parser will evaluate the 265: <block> or not. Helper function will be created for 266: making hints and other study aids easy to contruct. 267: </li> 268: <li> 269: <import> causes the parse to read an additional 270: file in and parse it as if the entire text of file had 271: existed at the location of the <import> 272: </li> 273: <li> 274: <script> the enclosed body of text is parsed 275: directly in a safe Perl enviroment. Variables set here are 276: available throught the rest of the problem code, but all 277: actions taken persit only for the scope of the 278: <problem>. Except values which are expressly saved 279: and restored 280: </li> 281: <li> 282: <while> implements a while loop, required argument 283: condition is a perl scriptlet that when evaluated 284: results in a true or false value, on true the entirty of the 285: text between the whiles is parsed. The condition is tested 286: again, etc. If false it goes to the next node in the parse. 287: </li> 288: </ul> 289: </li> 290: <li> 291: Libraries 292: <ul> 293: <li> 294: <parserlib> the enclosed name is a file that 295: contains definition for new tags. 296: </li> 297: <li> 298: <scriptlib> the enclosed name is a file that 299: contains extensions to the parser. 300: </li> 301: </ul> 302: </li> 303: </ul> 304: 305: 306: <h2>CAPA compatability function Calls</h2> Please refer to the 307: CAPA manual for documentation on what these functions do. 308: <ul> 309: <li> random </li> 310: <li> random_normal </li> 311: <li> random_beta </li> 312: <li> random_gamma </li> 313: <li> random_poisson </li> 314: <li> random_exponential </li> 315: <li> random_chi </li> 316: <li> random_noncentral_chi </li> 317: <li> choose </li> 318: <li> var_in_tex </li> 319: <li> capa_id </li> 320: <li> class, section, set, problem, name, student_number </li> 321: <li> due_date, open_date, answer_date </li> 322: <li> to_string </li> 323: <li> sub_string </li> 324: <li> strlen </li> 325: <li> get_seed </li> 326: <li> set_seed </li> 327: <li> init_array </li> 328: <li> array_max, array_min </li> 329: <li> array_moments </li> 330: <li> to_int </li> 331: <li> format </li> 332: <li> pick </li> 333: <li> sin, cos, tan, asin, acos, atan, atan2 </li> 334: <li> sinh, cosh, tanh, asinh, acosh, atanh </li> 335: <li> j0, j1, jn, y0, y1, yn </li> 336: <li> log, log10 </li> 337: <li> exp, pow </li> 338: <li> erf, erfc </li> 339: <li> sqrt </li> 340: <li> min, max </li> 341: <li> abs, floor, ceil, sgn, mod, remainder </li> 342: <li> factorial </li> 343: <li> roundto </li> 344: <li> eval_formula </li> 345: <li> capa_id_plus </li> 346: <li> seat_number </li> 347: <li> duration </li> 348: <li> is_open, is_due, is_answer </li> 349: <li> managermode </li> 350: </ul> 351: 352: <hr> 353: <address><a href="mailto:albertel@marvin.lite.msu.edu">Guy Albertelli</a></address> 354:  355:  356: Last modified: Thu Dec 28 17:50:36 EST 2000 357:  358: </body> 359: </html>