-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alphapeptdeep Integration #3123
base: master
Are you sure you want to change the base?
Alphapeptdeep Integration #3123
Conversation
Something went wrong with the merge here. It shouldn't show changes from other PRs. Maybe try fetching latest master and rebasing your branch on it. Do you need help doing that?. |
My guess is that pushing "Update branch" will fix everything. |
868fde7
to
416c9d2
Compare
Yeah. Thanks for asking. I did a rebase which treated the updated changes and anything in between as new commits. I rolled back those changes and added the updates as a new commit. That fixed this branch. I will do a merge from master later on. |
3db9cca
to
b007485
Compare
On TeamCity the TestData test runs from an installed directory (installed with the WIX-based installer). Any non-vendor DLLs have to be added into |
…IResources into ToolsResources
a4971e8
to
7812cb5
Compare
…ry with alphapeptdeep" This reverts commit 5c487ab. Tempororily remove this commit to make TeamCity build succeeds
…om skyline document
…alphapeptdeep cli to build library
… library file to be skyline compatible
…support' of github.com:ProteoWizard/pwiz into Skyline/work/20240816_pythoninstaller_with_virtual_env_support
How are we testing the GPU support? |
We could test nightly only and even on one specific machine. Though, many
machines have NVIDIA GPUs.
Let’s really try to tie off new features and get a milestone merge in that
is complete and well tested.
…On Fri, Jan 24, 2025 at 7:23 AM Matt Chambers ***@***.***> wrote:
How are we testing the GPU support?
—
Reply to this email directly, view it on GitHub
<#3123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYBWUHEN6EDILBT5KQSK3D2MJLF3AVCNFSM6AAAAABMTVTTOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSG44DMOBTGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Currently I am testing on my laptop with NVIDIA and Macs2 to test on a node without an NVIDIA. Automated tests on nodes with NVIDIA will answer "No" to installing Cuda libraries and will not enable GPU support after detecting the card. GPU library installation only has to happen once for every new version of Cuda and is done as an addendum to the python install. I am not integrating any new features, just focusing on testing going forward to the merge.
…On Friday, January 24th, 2025 at 7:23 AM, Matt Chambers ***@***.***> wrote:
How are we testing the GPU support?
—
Reply to this email directly, [view it on GitHub](#3123 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BLXOSXE7JMXRICAAL7CUD3T2MJLF3AVCNFSM6AAAAABMTVTTOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSG44DMOBTGQ).
You are receiving this because you commented.Message ID: ***@***.***>
|
… during testing. Also changes to the PythonTestUtil related to order of Message Dialogs presented during Python Install and Nvidia configuration.
…setup. Implement local functions for labeling precursors to address build message : WARNING: Found prohibited use of "using.*(pwiz\.Skyline\.(Alerts|Controls|.*UI)|System\.Windows\.Forms|pwiz\.Common\.GUI)" (Skyline model code must not depend on UI code) at C:\pwiz\pwiz_tools\Skyline\Model\AlphaPeptDeep\AlphapeptdeepLibraryBuilder.cs(14) using pwiz.Skyline.Controls.SeqNode;
…rk/20240816_pythoninstaller_with_virtual_env_support
…to PythonInstaller revealed by BPratt's buddy testing
…rk/20240816_pythoninstaller_with_virtual_env_support
…yline/work/20240816_pythoninstaller_with_virtual_env_support and address issues brought up during buddy testing # Resolved Conflicts: # pwiz_tools/Skyline/SettingsUI/PeptideSettingsUI.cs
@@ -10,7 +29,7 @@ | |||
namespace pwiz.SkylineTestUtil | |||
{ | |||
[TestClass] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop this - this isn't a test, it's code supporting tests
private void RunNvidiaDialog(MultiButtonMsgDlg nvidiaDlg) | ||
{ | ||
nvidiaDlg.ClickNo(); | ||
MessageDlg confirmDlg = WaitForOpenForm<MessageDlg>(600000); | ||
MessageDlg confirmDlg = AbstractFunctionalTest.WaitForOpenForm<MessageDlg>(600000); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should use the change I supplied privately:
// We aren't running with admin privilege so we have to say no to the offer to install nvidia libraries var confirmDlg = AbstractFunctionalTest.ShowDialog<MessageDlg>(nvidiaDlg.ClickNo, 600000);
As it is, you're running UI code on the test thread, which causes intermittent failures
using System; | ||
/* | ||
* Maintainer: David Shteynberg <david.shteynberg .at. proton.me>, | ||
* MacCoss Lab, Department of Genome Sciences, UW |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Maintainer" isn't something you'll find anywhere in the rest of the code. Just use "Author", which is Skyline-speak for "owner" or "knows more about it than anyone else, presumably". And, use your proteinms email.
private void RunNvidiaDialog(MultiButtonMsgDlg nvidiaDlg) | ||
{ | ||
nvidiaDlg.ClickNo(); | ||
MessageDlg confirmDlg = WaitForOpenForm<MessageDlg>(600000); | ||
MessageDlg confirmDlg = AbstractFunctionalTest.WaitForOpenForm<MessageDlg>(600000); | ||
Assert.AreEqual(string.Format(ToolsUIResources.PythonInstaller_OkDialog_Successfully_set_up_Python_virtual_environment), | ||
confirmDlg.Message); | ||
confirmDlg.OkDialog(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, you should use the change I provided privately:
AbstractFunctionalTest.OkDialog(confirmDlg, confirmDlg.OkDialog);
this achieves two things - runs UI code on the UI thread, and makes sure the dialog is completely dismissed before moving along.
Console.WriteLine(@"Info: Successfully set LongPathsEnabled registry key to 1"); | ||
_undoRegistry = true; | ||
MessageDlg okDlg = WaitForOpenForm<MessageDlg>(); | ||
MessageDlg okDlg = AbstractFunctionalTest.WaitForOpenForm<MessageDlg>(); | ||
okDlg.OkDialog(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is actually reachable code (unless running Skyline as admin, which would be unusual) but this line should be
AbstractFunctionalTest.OkDialog(okDlg, okDlg.OkDialog);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if there isn't a way we could let a user who does have sufficient rights to set that registry key - launch a tiny app that does only that, and only works if the user clicks through the OS-provided query about it
…rom running AlphaPeptDeep will be logged to the Immediate Window
…yline/work/20240816_pythoninstaller_with_virtual_env_support
…yline/work/20240816_pythoninstaller_with_virtual_env_support
…s when "Cancel" is pressed. Update to Python installer to improve user experience.
…rk/20240816_pythoninstaller_with_virtual_env_support
…n SkylineProcessRunner. Refactor PythonInstallerUI a to improve readability. ProcessRunner will not report message to the dialog box when logging to ImmediateWindow to address Brian's concern.
PythonInstaller
toPythonInstallerLegacyDlg
PythonInstaller
implementation to support Python virtual environmentPythonInstaller
implementation