fsthiprecision still giving 3 decimal places
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 207
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
I am trying to obtain more than three decimals with smartpca. I am using the fsthiprecision option that theoretically gives six, but it still gives me the same output as by default. Could you please help me?
INPUT PARAMETERS
genotypename: input.ped
snpname: input.map
indivname: input.ped
evecoutname: PCA.evec
evaloutname: PCA.eval
altnormstyle: NO
numoutevec: 10
numoutlieriter: 0
familynames: NO
fstonly: YES
fsthiprecision: YES
maxpops: 200
phylipoutname: out.fst
My smartpca version is 13050.
Thanks in advance!
André
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with smartpca version 13050 using the listed parameters and input.ped/input.map, focusing on fsthiprecision and the out.fst output. Trace where smartpca formats FST values and verify that enabling the option produces six decimal places; done means the output differs from the default three-decimal format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100