question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Scout demo database doesn't load Ancestry (pred.) or Parenthood

See original GitHub issue

Hi all, thankyou for the great software!

I’m having loading some values into scout that should be included through these variables/files in the config file:

peddy_ped: scout/demo/643594.peddy.ped
peddy_ped_check: scout/demo/643594.ped_check.csv
peddy_sex_check: scout/demo/643594.sex_check.csv

When the demo database is loaded, scout doesn’t appear to be grabbing the values from these files to populate the Ancestry (pred.) and Parenthood columns of the ‘Individuals’ panel in the 643594 case (see images below):

scout_parenthood_loading scout_parenthood_loading_2

  • No error messages are thrown when creating or serving the database.

  • I’m using scout version 4.19 and python 3.7.6 installed within a conda environment.

Please let me know if you require any further details from me, thanks in advance for your help!

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
northwestwitchcommented, Aug 11, 2020

Hi again @leahkemp , I’ve found out what the problem is.

The command scout setup demo at the moment doesn’t load the peddy info (thanks for opening the issue!), but this will be fixed in the next Scout release (later thin month).

The workaround for the demo case (or your clinical cases) is: Rename 2 fields in the config file:

  • peddy_ped_check --> peddy_check
  • peddy_sex_check --> peddy_sex

And then load the demo case with the command scout --demo load case scout/demo/643594.config.yaml

The command for one of your own cases would be scout (--demo) load case path/to/your/config/file

This way it should work. I’m going to fix the naming of these fields also in the documentation. Sorry for the inconvenience, and thanks again for your feedback!

0reactions
leahkempcommented, Aug 11, 2020

Fantastic the workaround has worked perfectly for our clinical data! Many thanks for your help @northwestwitch!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting Ancestry® Apps
Follow the steps in this article if your Ancestry® app is: crashing or closing unexpectedly; not responding; not opening ...
Read more >
DNA Activation Troubleshooting - Ancestry Support
You can see if your test is activated by signing into your account and clicking the DNA tab. Click AncestryDNA® or Your DNA...
Read more >
Fixing Page or Button Problems on Ancestry®
Follow the steps below if you're having any of these problems: Broken or missing buttons; Missing tabs; Pages not saving; Pages not loading,...
Read more >
Troubleshooting Issues - Ancestry Support
Fixing Page or Button Problems on Ancestry®​​ If you're seeing error messages, display problems, or broken buttons or links, try clearing your browser's...
Read more >
Waiting for DNA Results - Ancestry Support
If you've returned your AncestryDNA® sample, here's what you can expect: Right away: If you haven't activated your DNA kit (entering the code ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found