Error on 'Assigning protein identifications to layers' with group FDR

[alessandro-vai]

Hello,

I'm encountering a runtime error when attempting to use the group FDR functionality in Philosopher v5.1.2. The process fails at the step "Assigning protein identifications to layers" with the following error:

panic: runtime error: slice bounds out of range [-1:]

goroutine 1 [running]:
github.com/Nesvilab/philosopher/lib/rep.(*Evidence).UpdateLayerswithDatabase(0xc0000fe008, {0xc0000be050, 0x50}, {0x7fffb08e5ca3, 0x4})
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/lib/rep/updater.go:540 +0x28b6
github.com/Nesvilab/philosopher/lib/fil.Run({{0xc0000ba000, 0x24}, {0xc0000be000, 0x50}, {0xc0000ba030, 0x29}, {0xc0000c0000, 0x5f}, {0xc0000c0060, 0x56}, ...})
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/lib/fil/fil.go:178 +0x1085
github.com/Nesvilab/philosopher/cmd.init.func6(0xc0000ae200?, {0xb82828?, 0x4?, 0xb8282c?})
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/cmd/filter.go:47 +0x4b7
github.com/spf13/cobra.(*Command).execute(0x26b9b80, {0xc000099860, 0xd, 0xd})
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/vendor/github.com/spf13/cobra/command.go:920 +0x867
github.com/spf13/cobra.(*Command).ExecuteC(0x26bbb20)
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/vendor/github.com/spf13/cobra/command.go:1044 +0x3a5
github.com/spf13/cobra.(*Command).Execute(...)
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/vendor/github.com/spf13/cobra/command.go:968
github.com/Nesvilab/philosopher/cmd.Execute()
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/cmd/root.go:35 +0x1a
main.main()
	E:/Projects/philosopher/phi-5.1.1_RC/philosopher/main.go:23 +0x85
Process 'PhilosopherFilter' finished, exit code: 2
Process returned non-zero exit code, stopping

The search runs without any issues using Philosopher v5.1.1 and the same versions of the other tools.

Thank you,
Alessandro

log.txt

[AimeeD90]

Hi @alessandro-vai, it's the same issue as #533, you can find the fixed version over there.

[alessandro-vai]

Yes, it's the same error. However, I'm still encountering it even with the fixed version.
It seems similar to this issue, but I'm running on Linux. I'm not sure whether the Linux version has been recompiled with the fix as well.

log.txt