Pick children window closing instantly, 23.1 bug?

support
Pick children window closing instantly, 23.1 bug? warham  2023-09-29 10:45
 

Hi,

I have been working on a file for a over a few days and today when I opened it and tried to open the pick children window, skyline stalls, uses 20% of my CPU for maybe 5 seconds and then the window opens and instantly closes so that I cannot use it. The file is other wise able to see the data, can access the data to generate the full scan data for example. The Pick children window was working on this file earlier, not sure how it might have become corrupted but closing and reopening both the file and skyline does not help. The modify peptide window is functioning properly as well. I'm not sure but the performance feels very much like a bug.

Best,
Lance

 
 
Nick Shulman responded:  2023-09-29 10:54
Can you send us your Skyline document?
In Skyline you can use the menu item:
File > Share
to create a .zip file containing your Skyline document and supporting files including extracted chromatograms.

If that .zip file is less than 50MB you can attach it to this support request. You can upload larger files here:
https://skyline.ms/files.url

Be sure to let me know which thing in the Targets tree you were trying to pick children on.

I have certainly seen some cases where it takes a really long time for the Child Picker window to come up. Sometimes this is caused by Skyline needing to read chromatogram peaks from the .skyd file in order to know what color dots to draw next to the transitions in the child picker. There are other times when it just takes a really long time because there are some many choices based on the enzyme or protein sequence.

If you remove all of the results from your Skyline document (Edit > Manage Results > Remove All) then the Pick Children window will probably come up faster, but, obviously, there are reasons that you would not want to to do that.

After I see your Skyline document I will probably be able to tell you why it is taking so long and I will try to fix it.
-- Nick