Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 42 – 46 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 47 – 49 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 51 – 55 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 56 – 58 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 60 – 62 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1LDL

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 63 – 67 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 70 – 72 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1LDR

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 75 – 77 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1LDR

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 79 – 81 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1LDR

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 85 – 87 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 88 – 90 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1LDR

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 95 – 97 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 99 – 103 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F5Y

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 113 – 115 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 121 – 123 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 124 – 126 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 129 – 131 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 138 – 142 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 143 – 147 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 148 – 151 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 152 – 154 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 156 – 158 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 160 – 162 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 163 – 165 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 168 – 170 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 173 – 176 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 177 – 179 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 181 – 183 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2FCW

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 189 – 191 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 201 – 204 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 205 – 207 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 208 – 211 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 212 – 214 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1AJJ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 217 – 219 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1AJJ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 222 – 224 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2LGP

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 226 – 228 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1AJJ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 241 – 243 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1D2J

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 244 – 246 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1D2J

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 247 – 249 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1D2J

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 251 – 253 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1D2J

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 254 – 258 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1D2J

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 260 – 264 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1D2J

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 265 – 267 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F8Z

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 268 – 270 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1F8Z

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 281 – 283 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1XFE

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 289 – 292 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1XFE

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 293 – 296 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1XFE

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 306 – 308 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1XFE

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 310 – 312 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1XFE

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 317 – 319 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 321 – 324 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 326 – 330 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 333 – 335 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 337 – 339 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 341 – 343 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1HZ8

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 345 – 347 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 348 – 350 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 351 – 353 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:2W2N

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined helical regions within the protein sequence.More...Helixi [Position(s)] 357 – 359 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1HJ7

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 363 – 369 [Length] 7 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1HJ7

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 372 – 374 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:3P5B

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 376 – 378 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1HJ7

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 381 – 385 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1HZ8

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 387 – 389 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:3P5B

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 392 – 394 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1HZ8

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 400 – 404 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 406 – 413 [Length] 8 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 420 – 423 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 427 – 435 [Length] 9 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 436 – 439 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 440 – 445 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 446 – 449 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 450 – 455 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 466 – 469 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 478 – 482 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 483 – 486 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 487 – 492 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 493 – 496 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 497 – 502 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 505 – 513 [Length] 9 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 519 – 525 [Length] 7 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 526 – 529 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 530 – 535 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 537 – 539 [Length] 3 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 541 – 546 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 552 – 556 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 563 – 569 [Length] 7 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 570 – 573 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 574 – 579 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 580 – 583 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 584 – 589 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 596 – 600 [Length] 5 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 602 – 605 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 606 – 614 [Length] 9 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined beta strands within the protein sequence.More...Beta strandi [Position(s)] 617 – 622 [Length] 6 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Feature key] Is used to indicate the positions of experimentally determined hydrogen-bonded turns within the protein sequence. These elements correspond to the DSSP secondary structure code ‘T’.More...Turni [Position(s)] 623 – 626 [Length] 4 [Description]

Output: Combined sources Manually validated information inferred from a combination of experimental and computational evidence. More… Manual assertion inferred from combination of experimental and computational evidencei PDB:1IJQ

LDLR - Low-density lipoprotein receptor precursor - Homo sapiens (Human)


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.comKanjinai furi wo shite woo yeah Kono mune no okutsuki ni mata hitotsu Towa ni iyasenai kizu wo fuyashite [English Translation]

Output: Lyrics from Animelyrics.comEven with the appearance of not caring ooh yeah In the graveyard of this heart there's still one wound Eternal life^ can't heal growing...

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.comJuujika no kage ga sasu woo yeah Itowashii unmei ni sakaratte Meshi ita kotori wo yami ni nigashita [English Translation]

Output: Lyrics from Animelyrics.comThe shadow of the cross reaches out ooh yeah To defy this detestable fate A small, blind bird was let loose into the darkness

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.comShoot ice bullet, shoot at the fate Kushibatta mama no Kuchibiru wo afureru...chi no aji Shoot ice bullet, shoot at the dark Kodoku no hate e to Aozameta hikigane hiku no sa zero in on [English Translation]

Output: Lyrics from Animelyrics.comShoot ice bullet, shoot at the fate As I grit my teeth The taste of blood...overflows from my lips Shoot ice bullet, shoot at the dark To put an end to this loneliness Pull the trigger and zero in on

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.comAshikubi ni sugaritsuku woo yeah Asamashii tamashii ga koi negau Shokuzai no ura no kao wo sukashite [English Translation]

Output: Lyrics from Animelyrics.comClinging to your ankle ooh yeah This wretched soul desires The opposite of atonement, to be able to hold my face to the light

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.comZetsubou e kashimuku no wa woo yeah Wazuka demo shinjite 'ta amasa darou? Fui ni okashikute usuku waratta [English Translation]

Output: Lyrics from Animelyrics.comSinking into despair ooh yeah Even if it was just a little you believed in generosity right? Suddenly it struck me as funny and I laughed weakly

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.comShoot ice bullet, shoot at the fate Wana naki wo utsu Kyouretsu na recoil shock...hiji wo daku Shoot ice bullet, shoot at the dark Ikite 'ru akashi wo Tsukamu made ochite mo yamenai keep it up [English Translation]

Output: Lyrics from Animelyrics.comShoot ice bullet, shoot at the fate Eliminate the trembles of fear and embrace the powerful recoil shock in your elbow Shoot ice bullet, shoot at the dark Catch the proof of your existence Even if it falls try to hold on and keep it up

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Original / Romaji Lyrics] Lyrics from Animelyrics.com...Hikari motome [English Translation]

Output: Lyrics from Animelyrics.com...Demand the light

Anime Lyrics dot Com - ICE BULLET - Zombie-Loan - Anime


Input: [Hook phase] Quick handler [mod_lua directive] LuaQuickHandler [Description]

Output: This is the first hook that will be called after a request has been mapped to a host or virtual host

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Translate name [mod_lua directive] LuaHookTranslateName [Description]

Output: This phase translates the requested URI into a filename on the system. Modules such as mod_alias and mod_rewrite operate in this phase.

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Map to storage [mod_lua directive] LuaHookMapToStorage [Description]

Output: This phase maps files to their physical, cached or external/proxied storage. It can be used by proxy or caching modules

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Check Access [mod_lua directive] LuaHookAccessChecker [Description]

Output: This phase checks whether a client has access to a resource. This phase is run before the user is authenticated, so beware.

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Check User ID [mod_lua directive] LuaHookCheckUserID [Description]

Output: This phase it used to check the negotiated user ID

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Check Authorization [mod_lua directive] LuaHookAuthChecker or LuaAuthzProvider [Description]

Output: This phase authorizes a user based on the negotiated credentials, such as user ID, client certificate etc.

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Check Type [mod_lua directive] LuaHookTypeChecker [Description]

Output: This phase checks the requested file and assigns a content type and a handler to it

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Fixups [mod_lua directive] LuaHookFixups [Description]

Output: This is the final "fix anything" phase before the content handlers are run. Any last-minute changes to the request should be made here.

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Content handler [mod_lua directive] fx. .lua files or through LuaMapHandler [Description]

Output: This is where the content is handled. Files are read, parsed, some are run, and the result is sent to the client

mod_lua - Apache HTTP Server Version 2.4


Input: [Hook phase] Logging [mod_lua directive] LuaHookLog [Description]

Output: Once a request has been handled, it enters several logging phases, which logs the request in either the error or access log. Mod_lua is able to hook into the start of this and control logging output.

mod_lua - Apache HTTP Server Version 2.4


Input: [0] top [2] Planned [1]

Output: Medium

Cosplay Island | View Costume | dan-dan - Hiccup


Input: [0] waistcoat [2] Planned [1]

Output: Medium

Cosplay Island | View Costume | dan-dan - Hiccup


Input: [0] wig [2] Complete [1]

Output: Low

Cosplay Island | View Costume | dan-dan - Hiccup


Input: [0] trousers [2] Planned [1]

Output: Low

Cosplay Island | View Costume | dan-dan - Hiccup


Input: [0] boots [2] Planned [1]

Output: Low

Cosplay Island | View Costume | dan-dan - Hiccup


Input: [0] belt [2] Planned [1]

Output: Low

Cosplay Island | View Costume | dan-dan - Hiccup


Input: [I am Seeking a] Needs Test [Woman] Not Completed [Dating] Not Completed [For]

Output: Chemistry

tutt10 Guitar, boxing, concerts, exercise..


Input: [I am Seeking a] Do you drink? [Woman] Socially [Dating] Want children [For]

Output: Do you want children?

tutt10 Guitar, boxing, concerts, exercise..


Input: [I am Seeking a] Marital Status [Woman] Divorced [Dating] No [For]

Output: Do you do drugs?

tutt10 Guitar, boxing, concerts, exercise..


Input: [I am Seeking a] Hair Color [Woman] Brown [Dating] Green [For]

Output: Eye Color

tutt10 Guitar, boxing, concerts, exercise..


Input: [I am Seeking a] Do you have a car? [Woman] Yes [Dating] Yes [For]

Output: Do you have children?

tutt10 Guitar, boxing, concerts, exercise..


Input: [I am Seeking a] Longest Relationship [Woman] Over 4 years [Dating] Very Ambitious [For]

Output: How ambitious are you?

tutt10 Guitar, boxing, concerts, exercise..


Input: [I am Seeking a] Pets [Woman] No Pets [Dating] Spanish [For]

Output: Second Language

tutt10 Guitar, boxing, concerts, exercise..


Input: [Specifications] How to Order Tile Samples [Description]

Output: You may order samples online or by phone. Sample must be purchased and shipping charges apply. When ordering samples please keep in mind there is no guarantee tile samples will match future orders do to the handmade process.


Input: [Specifications] Size [Description]

Output: Due to handmade nature, tiles may vary by up to ¼ in. Sizes are nominal; meaning that sizes vary from the actual.


Input: [Specifications] Body [Description]

Output: Red body bisque, irregular and concave (not perfectly flat).


Input: [Specifications] Crazed Effect [Description]

Output: Crazing effect refers to small cracks on the surface of a tile, characteristic which is inherent and may be visible before and/or after installation. However, over time this attribute may become more prominent or can be enhanced by using a contrasting colored grout.


Input: [Specifications] Tile Thickness [Description]

Output: ¼ in. thickness. Larger and smaller tiles may vary in thickness accordingly.


Input: [Specifications] Applications [Description]

Output: Suitable for all interiors of residential and commercial wall applications. Light-use flooring as accents or as a border to define an area. If used in moist areas, apply a penetrating sealer which forms an invisible barrier that is resistant to moisture and stains while allowing vapor to escape. Outdoor use is subject to climate. Talavera tiles are NOT frost proof.


Input: [Specifications] Recommended Grout Type and Width [Description]

Output: 1/4 in. grout line suggested. Use sanded grout when doing grout lines of 1/4 in. or more; and non-sanded grout when less than 1/4 in. We recommend to seal tile before grouting and to seal grout after installation. For further advice, contact your professional tile installer.


Input: [Specifications] Color, Size and Design Variation [Description]

Output: Slight variations are expected for all Talavera Tiles. For instance, size, color and design are all likely to vary due to the hand made process. Please note shades of color are seen differently on computer monitors and therefore customers should request a sample before making a final selection or purchase. Lot variation in size and color may be present from shipment to shipment. There is no guarantee that tiles ordered as add-ons will match those from the original orders.


Input: [Specifications] Installation Recommendations [Description]

Output: Lay out material prior to installation to properly blend and balance color. Due to size variation, we recommend to shuffle thru tile or several boxes before installation. The application of a penetrating sealer is recommended in accordance with the sealer manufacturer’s instructions to further enhance the durability of the tile. Note: Always perform a sample test on an inconspicuous area, before applying the sealer on an entire tiled surface.


Input: [Specifications] Further Installation Details [Description]

Output: Ceramic Tile Installation The successful installation of ceramic tiles is highly affected by the installation process. Tierra y Fuego strongly recommends hiring or consulting a skilled professional tile installer, even for small projects. Tierra y Fuego is not liable for tile that has been altered from its original state due to improper handling during the installation process. Inspect the tile prior to installation as installation signifies acceptance. For a successful installation of Tierra y Fuego’s ceramic tiles, please take note of the following recommendations: • Carefully choose a skilled tile installer. • Properly blend all tiles prior to installation. • Make sure the installer is informed of all the procedures and products; and carefully follows the manufacturer’s instructions of any solutions such as sealers, grout releases, and cleaners that may be used or come in contact with the tile during the installation process. • Seal tiles with a penetrating sealer of your choice prior to grouting. We recommend 511 Impregnator Sealer from Miracle Sealants Company for medium to dense porous surfaces. • One important consideration as part of the tile selection process is the color of the grout. Depending on the desired final overall look, there are three basic approaches to selecting the grout color: matching, contrasting, and neutral. Grout will affect the product’s final appearance. • Grout tile with sanded grout. Premixed epoxy grout is NOT recommended due to its viscosity. • Allow the entire tiled area to dry completely. Depending on environmental climate, it will typically take 24 hours to dry. • After the installation has been completed, seal the entire area once again with a penetrating sealer. • Note: Always test a small sample tile with the solutions that might be used during installation before applying to an entire area. This guide is intended to provide information on frequently asked questions. Opinions vary in the ceramic tile industry about the proper installation of ceramic tiles. However, since Tierra y Fuego tiles are porous they should be sealed with a penetrating sealer before and after grouting.


Input: [Specifications] Care Recommendations [Description]

Output: Clean with mild cleanser and damp cloth, do not use abrasive cleaners.


Input: [Specifications] How Much Extra Tile to Order [Description]

Output: Industry standard recommends adding on 5-10% additional tile to the tile needed to account for waste, special cuts, or other unforeseen problems. This is particularly important in complex installations. Specially with diagonal patterns.


Input: [Year] Summary (PDF) [Description]

Output: Summary of local elections in California


Input: [Year] Table A (PDF) [Description]

Output: Summary of outcomes of ballot measures by type of measure and county


Input: [Year] Table B (PDF) [Description]

Output: Summary of outcomes of ballot measures by topic of measure and county


Input: [Year] Table C (PDF) [Description]

Output: Summary of candidate election outcomes by type of office and incumbency for the state as a whole


Input: [Year] City Reports (PDF) [Description]

Output: Complete city report including all tables and text summaries of city offices and ballot measure outcomes


Input: [Year] County Reports (PDF) [Description]

Output: Complete county report including all tables and text


Input: [Year] School District Reports (PDF) [Description]

Output: Complete school district report including all tables and text


Input: [Year] 1997 Data (Excel) [Description]

Output: Data on all measures and all candidate race data


Input: [Description] The access token you can use to make requests on behalf of this Stripe account. Use it as you would any Stripe secret API key. This key does not expire, but may be revoked by the user at any time (you'll get a account.application.deauthorized webhook event when this happens). [Parameter]

Output: access_token


Input: [Description] The scope granted to the access token, depending on the scope of the authorization code and scope parameter. [Parameter]

Output: scope


Input: [Description] The livemode of the token. If true, the access_token can be used as a live secret key. If false, the access_token can be used as a test secret key. Depends on the livemode of the secret API key used to make the request. [Parameter]

Output: livemode


Input: [Description] Will always have a value of bearer. [Parameter]

Output: token_type


Input: [Description] Can be used to get a new access token of an equal or lesser scope, or of a different livemode (where applicable). [Parameter]

Output: refresh_token


Input: [Description] The unique id of the account you have been granted access to, as a string. [Parameter]

Output: stripe_user_id


Input: [Description] A publishable key that can be used with this account. Matches the livemode of the token. [Parameter]

Output: stripe_publishable_key


Input: [Parameter] Envelope2D [Mandatory] Y [Description]

Output: Contains the envelope for this mosaic formatted as LLCx,LLXy URCx,URCy (notice the space between the coordinates of the Lower Left Corner and the coordinates of the Upper Right Corner). An example is Envelope2D=432500.25,81999.75 439250.25,84999.75

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Parameter] LevelsNum [Mandatory] Y [Description]

Output: Represents the number of reduced resolution layers that we currently have for the granules of this mosaic.

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Parameter] Levels [Mandatory] Y [Description]

Output: Represents the resolutions for the various levels of the granules of this mosaic. Please remember that we are currently assuming that the number of levels and the resolutions for such levels are the same across alll the granules.

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Parameter] Name [Mandatory] Y [Description]

Output: Represents the name for this mosaic.

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Parameter] ExpandToRGB [Mandatory] N [Description]

Output: Applies to colormapped granules. Asks the internal mosaic engine to expand the colormapped granules to RGB prior to mosaicking them. This is needed whenever the the granules do not share the same color map hence a straight composition that would retain such a color map cannot be performed.

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Parameter] AbsolutePath [Mandatory] Y [Description]

Output: It controls whether or not the path stored inside the “location” attribute represents an absolute path or a path relative to the location of the shapefile index. Notice that a relative index ensure much more portability of the mosaic itself. Default value for this parameter is False, which means relative paths.

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Parameter] LocationAttribute [Mandatory] N [Description]

Output: The name of the attribute path in the shapefile index. Default value is location.

Using the ImageMosaic plugin — GeoServer 2.7.x User Manual


Input: [Value] D3DPTEXTURECAPS_ALPHA [Meaning]

Output: Alpha in texture pixels is supported.


Input: [Value] D3DPTEXTURECAPS_ALPHAPALETTE [Meaning]

Output: Device can draw alpha from texture palettes.


Input: [Value] D3DPTEXTURECAPS_CUBEMAP [Meaning]

Output: Supports cube textures.


Input: [Value] D3DPTEXTURECAPS_CUBEMAP_POW2 [Meaning]

Output: Device requires that cube texture maps have dimensions specified as powers of two.


Input: [Value] D3DPTEXTURECAPS_MIPCUBEMAP [Meaning]

Output: Device supports mipmapped cube textures.


Input: [Value] D3DPTEXTURECAPS_MIPMAP [Meaning]

Output: Device supports mipmapped textures.


Input: [Value] D3DPTEXTURECAPS_MIPVOLUMEMAP [Meaning]

Output: Device supports mipmapped volume textures.


Input: [Value] D3DPTEXTURECAPS_NONPOW2CONDITIONAL [Meaning]

Output: D3DPTEXTURECAPS_POW2 is also set, conditionally supports the use of 2D textures with dimensions that are not powers of two. A device that exposes this capability can use such a texture if all of the following requirements are met. The texture addressing mode for the texture stage is set to D3DTADDRESS_CLAMP. Texture wrapping for the texture stage is disabled (D3DRS_WRAP n set to 0). Mipmapping is not in use (use magnification filter only). Texture formats must not be D3DFMT_DXT1 through D3DFMT_DXT5. If this flag is not set, and D3DPTEXTURECAPS_POW2 is also not set, then unconditional support is provided for 2D textures with dimensions that are not powers of two. A texture that is not a power of two cannot be set at a stage that will be read based on a shader computation (such as the bem - ps and texm3x3 - ps instructions in pixel shaders versions 1_0 to 1_3). For example, these textures can be used to store bumps that will be fed into texture reads, but not the environment maps that are used in texbem - ps, texbeml - ps, and texm3x3spec - ps. This means that a texture with dimensions that are not powers of two cannot be addressed or sampled using texture coordinates computed within the shader. This type of operation is known as a dependent read and cannot be performed on these types of textures.


Input: [Value] D3DPTEXTURECAPS_NOPROJECTEDBUMPENV [Meaning]

Output: Device does not support a projected bump-environment loopkup operation in programmable and fixed function shaders.


Input: [Value] D3DPTEXTURECAPS_PERSPECTIVE [Meaning]

Output: Perspective correction texturing is supported.


Input: [Value] D3DPTEXTURECAPS_POW2 [Meaning]

Output: If D3DPTEXTURECAPS_NONPOW2CONDITIONAL is not set, all textures must have widths and heights specified as powers of two. This requirement does not apply to either cube textures or volume textures. If D3DPTEXTURECAPS_NONPOW2CONDITIONAL is also set, conditionally supports the use of 2D textures with dimensions that are not powers of two. See D3DPTEXTURECAPS_NONPOW2CONDITIONAL description. If this flag is not set, and D3DPTEXTURECAPS_NONPOW2CONDITIONAL is also not set, then unconditional support is provided for 2D textures with dimensions that are not powers of two.


Input: [Value] D3DPTEXTURECAPS_PROJECTED [Meaning]

Output: Supports the D3DTTFF_PROJECTED texture transformation flag. When applied, the device divides transformed texture coordinates by the last texture coordinate. If this capability is present, then the projective divide occurs per pixel. If this capability is not present, but the projective divide needs to occur anyway, then it is performed on a per-vertex basis by the Direct3D runtime.


Input: [Value] D3DPTEXTURECAPS_SQUAREONLY [Meaning]

Output: All textures must be square.


Input: [Value] D3DPTEXTURECAPS_TEXREPEATNOTSCALEDBYSIZE [Meaning]

Output: Texture indices are not scaled by the texture size prior to interpolation.


Input: [Value] D3DPTEXTURECAPS_VOLUMEMAP [Meaning]

Output: Device supports volume textures.


Input: [Value] D3DPTEXTURECAPS_VOLUMEMAP_POW2 [Meaning]

Output: Device requires that volume texture maps have dimensions specified as powers of two.


Input: [Artist] The Dead Milkmen [Title] If I Had a Gun [Album]

Output: Soul Rotation

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Dead Moon [Title] Pain For Pretty [Album]

Output: Stranded in the Mystery Zone

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Joe Christ and the Bigger Than God [Title] Loaded Gun [Album]

Output: Loaded Gun b/w Fire of Love

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] The New Christs [Title] Like a Curse [Album]

Output: Detritus

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] New Model Army [Title] Western Dream [Album]

Output: The Ghost of Cain

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Blyth Power [Title] Signalman White [Album]

Output: Paradise Razed

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Mischief Brew [Title] Bang-Up Policework [New] ✔ [Album]

Output: Rhapsody for Knives

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] No Means No [Title] Body Bag [Album]

Output: You Kill Me

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] The Gun Club [Title] Bill Bailey [Album]

Output: Mother Juno

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Northern Liberties [Title] Live Again (with Tom Adams) [New] ✔ [Album]

Output: Collaborations

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Murder City Devils [Title] Dear Hearts [Album]

Output: R.I.P.

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Kid Congo and the Pink Monkey birds [Title] Lamonts Requim [New] ✔ [Album]

Output: Haunted Head

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Human Eye [Title] Into Unknown [New] ✔ [Album]

Output: Into Unknown

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Alec K. Redfearn and the Eyesores [Title] The Seven and Six [Album]

Output: Sister Death

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Red Dons [Title] A Forced Turning Point [Album]

Output: A Forced Turning Point

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Roman Holiday [Title] Burial Ground [Album]

Output: Demo 2013

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Bugs and Rats [Title] Open Doors [New] ✔ [Album]

Output: Get that Fucking Light Outta My Face

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Lost Sounds [Title] Total Destruction [Album]

Output: Lost Lost

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] The Hex Dispensers [Title] A Brain Inside a Jar [Album]

Output: Winchester Mystery House

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Artist] Lame Drivers [Title] Last Call for Violence [New] ✔ [Album]

Output: Cruisin' Classics

Talk of the Town on Mon 7/8/13 | WKDU Philadelphia 91.7FM


Input: [Patent #] 2012/0090017 [Description]

Output: Secure Push and Status Communication between Client and Server Systems and methods of authentication and authorization between a client, a server, and a gateway to facilitate communicating a message between a client and a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090016 [Description]

Output: Method and apparatus for registering agents onto a virtual machine monitor A method for managing an agent includes verifying an integrity of the agent in response to a registration request. Memory protection is provided for the agent...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090015 [Description]

Output: DEVICE AND METHOD FOR AUTHENTICATING BIOLOGICAL INFORMATION An biological-information authentication device includes, a biological-information reading section configured to read biological information; a comparing...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090014 [Description]

Output: ACCESS CONTROL APPARATUS, INFORMATION MANAGEMENT APPARATUS, AND ACCESS CONTROL METHOD An access control apparatus that controls access to an information management apparatus that stores configuration elements and relationship elements indicating...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090013 [Description]

Output: Unified management method and system for channel service as well as services on demand of stream media The present invention provides a unified management method system for channel service as well as service on demand of stream media, which belong to the...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090012 [Description]

Output: EVENT BOOKING MECHANISM A mechanism for booking events comprising an event broker, one or more event managers and one or more action handlers. In one embodiment, the event broker is...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090011 [Description]

Output: CONTENT UPLOAD SYSTEM AND CONTENT DISTRIBUTION SERVER A content upload system includes: a content distributing server that is installed in an airplane and distributes audio-video contents into the airplane; and a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090010 [Description]

Output: SYSTEM AND METHOD FOR 360 DEGREE SITUATIONAL AWARENESS IN A MOBILE ENVIRONMENT A method for providing situational awareness for a transport vehicle includes receiving a plurality of sensory inputs from cameras positioned about the...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090009 [Description]

Output: Video Assets Having Associated Graphical Descriptor Data Graphical descriptor data associated with a particular video asset may include data for one or more graphical descriptor images and graphical descriptor...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090008 [Description]

Output: METHOD AND SYSTEM FOR PRESELECTING MULTIMEDIA CONTENT A method and system for remote control at a client of a multimedia content distribution network (MCDN) enables a user to add desired multimedia program listings...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090007 [Description]

Output: PERSONALIZED TELEVISION GUIDE A system is configured to: receive identification information from a client device; identify a corresponding profile based on the identification information,...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090006 [Description]

Output: TELEVISION AND GENERATING METHOD OF ELECTRONIC PROGRAM GUIDE MENU THEREOF A generating method of generating an electronic program guide menu of a television includes the following steps: providing a main tuner for receiving a first...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090005 [Description]

Output: Holographic 3D Display Disclosure is directed to projecting holographic images in connection with a program service such as cable or satellite television. In one instance, the...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090004 [Description]

Output: DISPLAY APPARATUS AND METHOD FOR CONTROLLING THE DISPLAY APPARATUS A multifunctional display device includes a processor to control simultaneously display of visual information and monitoring information on a same screen. The...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090003 [Description]

Output: Thought Control of Set Top Box Disclosure is directed to commanding a content receiver by interpreting brainwave patterns that are captured from a user of the content receiver. The user's...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090002 [Description]

Output: DIGITAL BROADCAST RECEPTION DEVICE AND DIGITAL BROADCAST RECEPTION METHOD Disclosed are a digital broadcast reception device and digital broadcast reception method which can quickly present a data broadcast presentation screen once a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090001 [Description]

Output: APPARATUS HAVING MULTIMEDIA INTERFACE AND NETWORK ACCESS MANAGEMENT INTEGRATED THEREIN An apparatus includes a multimedia interface module and a network module. The multimedia interface module has a plurality of connection ports including at least...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0090000 [Description]

Output: Implementation of media content alteration A classification method and system for possible content alteration of a media work may include criteria regarding content that is feasible for alteration. Such...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089999 [Description]

Output: Metadata Origination Verification One embodiment may take the form of a method for verifying metadata associated with programming content. The method may include receiving a first metadatum...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089998 [Description]

Output: VIDEO SERVICE BLACKOUT EVENTS A method includes receiving, at a component of a multimedia content distribution system, a command including blackout information related to a first version of...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089997 [Description]

Output: SHARED PLANNER An improved media system is provided for sharing, accessing and managing stored media content between a plurality of networked Set-Top Boxes (STB). Aspects...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089996 [Description]

Output: CATEGORIZATION OF A MOBILE USER PROFILE BASED ON BROWSE AND VIEWING BEHAVIOR A system for categorization of a mobile user profile based on a browse and viewing behavior of a user includes (a) using data of a wireless provider to...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089995 [Description]

Output: DISK APPARATUS A disk device of the invention is provided with a trigger member rotated by being contacted with and pressed by a disk having a different diameter to be...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089994 [Description]

Output: OBJECT ORIENTED COMPONENT AND FRAMEWORK ARCHITECTURE FOR SIGNAL PROCESSING A signal intelligence system comprising a plurality of software components that are programmable to provide a signal intelligence function. The signal...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089993 [Description]

Output: User Data Convergence (UDC) Notification Management A method and arrangement in a User Data Repository, UDR, (30) for selecting an Application Front End (34a-34e) in a communication network to receive an event...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089992 [Description]

Output: USER INTERACTION SUPPORT ACROSS CROSS-ENVIRONMENT APPLICATIONS Cross-environment rendering and user interaction support provide a seamless computing experience in a multi-operating system computing environment. The...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089991 [Description]

Output: SYSTEM AND METHOD FOR IDENTIFYING CONTENTION OF SHARED RESOURCES IN A RUNTIME SYSTEM A system and computer-implemented method for determining a runtime of a thread of an application. Synchronization events for a first thread of an application...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089990 [Description]

Output: SYSTEM AND METHOD FOR REPORTING A SYNCHRONIZATION EVENT IN A RUNTIME SYSTEM OF A COMPUTER SYSTEM A system and computer-implemented method for reporting a synchronization event in a runtime system of a computer system. A synchronization primitive in a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089989 [Description]

Output: SYSTEMS AND METHODS FOR EXECUTING AND IMPLEMENTING COMPUTER PROCESSES IN PROCESS ENVIRONMENTS In at least one embodiment a computer implemented method is disclosed. A computer process is extracted from a first environment including a unique process...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089988 [Description]

Output: HOSTING NON-MESSAGING WORKFLOWS IN A MESSAGING HOST A workflow hosting system is described herein that allows non-messaging workflows to be hosted by a message-based service host. The system provides a host...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089987 [Description]

Output: METHODS, APPARATUS, AND SYSTEMS TO ACCESS RUNTIME VALUES OF OBJECT INSTANCES In one embodiment, a plurality of executable instructions is stored at a first software module. The plurality of executable instructions are collectively...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089986 [Description]

Output: PROCESS POOL OF EMPTY APPLICATION HOSTS TO IMPROVE USER PERCEIVED LAUNCH TIME OF APPLICATIONS Various embodiments enable a device to create a pool of at least one empty application. An empty application can be configured to contain resources that are...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089985 [Description]

Output: Sharing Sampled Instruction Address Registers for Efficient Instruction Sampling in Massively Multithreaded... Sampled instruction address registers are shared among multiple threads executing on a plurality of processor cores. Each of a plurality of sampled instruction...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089984 [Description]

Output: Performance Monitor Design for Instruction Profiling Using Shared Counters Counter registers are shared among multiple threads executing on multiple processor cores. An event within the processor core is selected. A multiplexer in...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089983 [Description]

Output: ASSESSING PROCESS DEPLOYMENT System and methods for assessing process deployment are described. In one implementation, the method includes collecting at least one metric value associated...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089982 [Description]

Output: SUPPORTING HETEROGENEOUS VIRTUALIZATION Machine-readable media, methods, apparatus and system are described. In some embodiments, a virtual machine monitor of a computer platform may comprise a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089981 [Description]

Output: METHOD AND SYSTEM FOR POWER MANAGEMENT IN A VIRTUAL MACHINE ENVIRONMENT WITHOUT DISRUPTING NETWORK CONNECTIVITY A method for power management. The method includes gathering resource usage data for a first blade and a second blade on a blade chassis, migrating each virtual...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089980 [Description]

Output: ALLOCATING VIRTUAL MACHINES ACCORDING TO USER-SPECIFIC VIRTUAL MACHINE METRICS The performance monitoring system allocates virtual machines to users or user sessions according to a user categorization that is determine using user session...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089979 [Description]

Output: Performance Monitor Design for Counting Events Generated by Thread Groups A number of hypervisor register fields are set to specify which processor cores are allowed to generate a number of performance events for a particular thread...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089978 [Description]

Output: METHOD FOR MANAGING APPLICATIONS OF PORTABLE DEVICES A method for managing applications of a portable device by a computer electrically connected to the portable device is provided, wherein the computer connects...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089977 [Description]

Output: METHOD AND APPARATUS FOR PERFORMING SERVICE IN PLURALITY OF DEVICES BASED ON WIDGET MIGRATION A service performing method and a service requesting method are provided. The service performing method includes receiving from a second device a message...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089976 [Description]

Output: Integrating Software Components Aspects of the subject matter described herein relate to integrating software components. In aspects, a previously created component is inserted into a target...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089975 [Description]

Output: Electronic Device An electronic apparatus is provided that can include a first downloader downloading a replacement control program from an external host computer by way of a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089974 [Description]

Output: USER TERMINAL DEVICE AND SERVICE PROVIDING METHOD THEREOF A method for providing a service in a user terminal device, which includes downloading a service hub program, installing the service hub program, generating an...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089973 [Description]

Output: SMART PATCH DELIVERY SYSTEM Software fix packs and/or APAR's are maintained at a server for use on a requesting computer system. The requesting computer system makes a request for a...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089972 [Description]

Output: Image Based Servicing Of A Virtual Machine An invention is disclosed for preserving state in a virtual machine when patching the virtual machine (VM). In an embodiment, when a deployment manager that...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089971 [Description]

Output: CREATING A SOFTWARE PRODUCT FROM A SOFTWARE APPLICATION A computer-usable storage medium having instructions embodied therein that when executed cause a computer system to perform a method for creating a product. The...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089970 [Description]

Output: APPARATUS AND METHOD FOR CONTROLLING LOOP SCHEDULE OF A PARALLEL PROGRAM A compiling apparatus and method are provided. The compiling apparatus includes a first setting unit that sets a first parameter of a parallel programming model...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089969 [Description]

Output: DECLARATIVE PROGRAMMING MODEL WITH A NATIVE PROGRAMMING LANGUAGE An execution environment in a computer system supports a declarative programming model where user code is written with a query syntax in a native programming...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [Patent #] 2012/0089968 [Description]

Output: RUNTIME AGNOSTIC REPRESENTATION OF USER CODE FOR EXECUTION WITH SELECTED EXECUTION RUNTIME An execution environment in a computer system allows user code to be executed using multiple execution runtimes. The execution environment translates the user...

Applications filed at Apr 12 2012 | Secure Push and Status Communication between Client and Server | Patents.com


Input: [1] Type [2] Description [0]

Output: Field


Input: [1] Number [2] height of the image in pixels [0]

Output: height


Input: [1] Number [2] width of the image in pixels [0]

Output: width


Input: [1] Number [2] Y-Axis value for the bottom of the image (default: 0) [0]

Output: ymin


Input: [1] Number [2] Y-Axis value for the top of the image (default: auto) [0]

Output: ymax


Input: [1] Number [2] Number of buckets in the vertical dimension [0]

Output: nbuckets


Input: [1] Array [2] Array of field values to highlight, isolate or exclude [0]

Output: selected


Input: [1] Boolean [2] If true, only draw selected values [0]

Output: isolate


Input: [1] Boolean [2] If true, don't draw selected values at all [0]

Output: exclude


Input: [1] Array [2] Array of colors for highlighting selected field values [0]

Output: hues


Input: [1] Boolean [2] highlight all field values (possibly reusing hues) [0]

Output: decompose_all


Input: [Pos] QB [Who is Eligible] Only quarterbacks [What it Means]

Output: Quarterback

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] RB [Who is Eligible] Only running backs [What it Means]

Output: Running Back

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] WR [Who is Eligible] Only wide receivers [What it Means]

Output: Wide Receiver

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] TE [Who is Eligible] Only tight ends [What it Means]

Output: Tight End

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] W/R [Who is Eligible] Any wide receiver or running back [What it Means]

Output: Wide Receiver/Running Back

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] W/T [Who is Eligible] Any wide receiver or tight end [What it Means]

Output: Wide Receiver/Tight End

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] Q/WR/RB/TE [Who is Eligible] Any quarterback, wide receiver, running back or tight end [What it Means]

Output: Quarterback/Wide Receiver/Running Back/Tight End

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] WR/RB/TE [Who is Eligible] Any wide receiver, running back or tight end [What it Means]

Output: Wide Receiver/Running Back/Tight End

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] K [Who is Eligible] Only kickers [What it Means]

Output: Kicker

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] DEF [Who is Eligible] Only team defenses [What it Means]

Output: Defensive Team

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] D [Who is Eligible] Any defensive player [What it Means]

Output: Defensive Player

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] DL [Who is Eligible] Only defensive linemen [What it Means]

Output: Defensive Lineman

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] DB [Who is Eligible] Only defensive backs [What it Means]

Output: Defensive Back

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] LB [Who is Eligible] Only linebackers [What it Means]

Output: Linebacker

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] CB [Who is Eligible] Only corner backs [What it Means]

Output: Corner Back

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] S [Who is Eligible] Only safties [What it Means]

Output: Safety

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Pos] BN [Who is Eligible] Any player [What it Means]

Output: Bench

Fantasy Points Against | Fantasy Football | Yahoo Sports


Input: [Field] Community string [Description]

Output: Name of the SNMP community string. Restriction: No spaces allowed.

Cisco Unified MeetingPlace, Release 7.0 -- Add SNMP Community String Page - DocWiki


Input: [Field] Accept SNMP packets from any host [Description]

Output: Allows the SNMP community string to accept SNMP packets from any host.

Cisco Unified MeetingPlace, Release 7.0 -- Add SNMP Community String Page - DocWiki


Input: [Field] Accept SNMP packets only from these hosts [Description]

Output: Allows the SNMP community string to accept SNMP packets only from hosts that you specify.

Cisco Unified MeetingPlace, Release 7.0 -- Add SNMP Community String Page - DocWiki


Input: [Field] Host IP address [Description]

Output: If you choose the Accept SNMP packets only from these hosts radio button, enter an IP address and click Insert to allow the SNMP community string to accept SNMP packets from this host.

Cisco Unified MeetingPlace, Release 7.0 -- Add SNMP Community String Page - DocWiki


Input: [Field] Host IP addresses [Description]

Output: If you choose the Accept SNMP packets only from these hosts radio button, this field lists all hosts from which this SNMP community string can accept SNMP packets. To remove a host from this list, highlight the IP address and click Remove.

Cisco Unified MeetingPlace, Release 7.0 -- Add SNMP Community String Page - DocWiki


Input: [Field] Access privileges [Description]

Output: The access privilege given to this SNMP community string. Access privileges provide security by restricting the ability to alter the Cisco Unified MeetingPlace system.

Cisco Unified MeetingPlace, Release 7.0 -- Add SNMP Community String Page - DocWiki


Input: Total Loss No total loss reported to CARFAX. [Owners 1-2] No Issues Reported [Owner 4] No Issues Reported [Owner 3]

Output: No Issues Reported

CARFAX Vehicle History Report for this 2008 SCION TC: JTKDE167980238981


Input: Structural Damage No structural damage reported to CARFAX. [Owners 1-2] No Issues Reported [Owner 4] No Issues Reported [Owner 3]

Output: No Issues Reported

CARFAX Vehicle History Report for this 2008 SCION TC: JTKDE167980238981


Input: Airbag Deployment No airbag deployment reported to CARFAX. [Owners 1-2] No Issues Reported [Owner 4] No Issues Reported [Owner 3]

Output: No Issues Reported

CARFAX Vehicle History Report for this 2008 SCION TC: JTKDE167980238981