By definition, an integer is a whole number, i.e. without a decimal point. Also, from a biological point of view it makes little sense - you cannot have 12.4 base pairs, or 12.4 repeats of a microsatellite (though imperfect repeats are possible, but you need to code them differently).

You need to bin your results, I recommend TANDEM software (Matschiner M, Salzburger W. TANDEM: integrating automated allele binning into genetics and genomics workflows).

Hi,

as Christian pointed, you have to work with "whole numbers" in the case you want to analyse your genotypic data. So, you need to round up/down allele sizes.

P.S. some software cannot process decimal values separated with "comma". You have to change it to "a dot". I think this is the case how Arlequin handles decimal values.

Mr. Majesky

The decimal points are crucial when working with Y-STR values because each value such as 13,2 and 13 represent a unique allele frequency and thats why the rounding option would drop the resolution significantly. However the values with decimal points are applicable for autosomal samples so I suppose there is a logic I am missing in comprehension for uni parental markers. 

I have also tried to replace comma with dot and vice-versa, same results. 

Hi,

If those numbers are alleles, you can artificially recode them (e.g. 13=100; 13.2=101; 13.4=102; etc). Or you can use allele size instead of repeat numbers, which will be a whole number. Although following analyses will be restricted and you have to be careful with result interpretation. Anyway, I think Arlequin cannot handle genotypic data with decimal numbers. Christian made a good suggestion that you need to bin your alleles. Try to look on it.