grm | Hosts application metadata/repositories for arkOS

Your problem is a variant on classic contextual keyword vs identifier issue, it seems.

Either "value" should be a lexer rule, not a parser rule, it's too late otherwise, or you should reorder the rules (or both).

Hence using VALUE = NUMBER | STRING (lexer rule) instead of lower case value (grammar rule) will help. The order of the lexer rules are also important, usually definition of ID ("VALUE" in your code) comes after keyword definitions.

See also : 'IDENTIFIER' rule also consumes keyword in ANTLR Lexer grammar

Your assertion that the max() function does not work with alphanumeric values is incorrect. However, the XSLT processor needs to be aware of the data type of the compared values.

Consider the following minimized example:

XML

I don't know which kind of output you need, but this selects the value you are looking for :

XSLT 2.0

Having asked the same question on the pymc3 discours pages. The developers responded and the reason for the above error is that for pm.sample_prior_predictive to work, one needs the random() method, which is only implemented for the GRM. However, pm.sample works just fine.

You have to double the brackets if you want to make a wildcard inside an expand function:

expand("path/snpgrm_chr{{chromosome}}.grm.{ext}", ext=["gz", "id"])

here, {{chromosome}} is a wildcard, {ext} is just a placeholder for the argument of the expand function

Your code has non-standard characters in some of the white space, including right after K;

1 and 2 would correspond to values from the first two columns in a text file.

each pair without repetition

So let's walk through this process:

1. We repeat the first column from the file times the file length
2. We repeat each value (each line) from the second column from the file times the file length
3. We join the repeated columns -> we have all combinations
4. We need to filter "repetitions", we can just join the file with the original file and filter out repeating columns
5. So we get each pair without repetitions.
6. Then we just read the file line by line.

The script:

After a while that nested loop approach is going to get hard to follow. If you plan on doing much of this type of processing then you really need to reduce the volume of code in your main method and make it easier to follow. The code below might seem over-worked, but the smaller re-usable parts only get written once, then you can re-use them as needed from other parts of your code.

Now your main sub now only does one thing, and you can much more easily read the code to figure out what that is.

Try to only allow the re-rendering to happen after the zoom by setting updateOnReleaseOnly to true.