Rappsilber-Laboratory / build-xiview

GNU General Public License v3.0
2 stars 0 forks source link

Incorporate Crosslink Quantification #84

Closed xLinkKnight closed 2 years ago

xLinkKnight commented 2 years ago

Feature Addition - Allow for the visualization of crosslink quantification information

Our group has been doing a lot more relative quantification experiments involving DSSO/DMTMM and TMT. Our primary search engine is XlinkX in PD. It would advantageous if there was a way to visualize the change in crosslink abundance through xiView. Could connections shown in the network map, circle plot, and PDB structure view be shown differently based on change in abundance? An example would be to change the color (positive or negative change) and thickness (gradient, fold change). These parameters can be generated by the user and added as columns in the uploaded spreadsheet.

colin-combe commented 2 years ago

there is some support for this - from the top main menu click IMPORT > EDGE METADATA (see https://xiview.org/xidocs/html/import/crossmeta.html) let me know if you have problems, cheers, colin

xLinkKnight commented 2 years ago

Thank you for the guide. I just have one problem concerning the processing/handling of the hex color value.

I used a hex color value which corresponds to the abundance fold change of a given crosslink within my protein complex. The values I've used are as follows:

#FA9C9E
#FA9FA1
#FCF9FC
#FAA5A7
#FA9496
#FAAFB2
#FAA8AB
#FA9EA0
#5A8AC6
#5A8AC6
#5A8AC6
#F1F4FB
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6

However, I only see the following once loaded into xiView:

#5A8AC6
#5A8AC6
#FCF9FC
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6
#5A8AC6

May I ask why some colors (red) are omitted or switched to more "blue" values? Please let me know if I'm doing something wrong. Thanks.

colin-combe commented 2 years ago

ok... that sounds pretty weird, something may be broken, i'll check.

I'll probably need to test by using your data and your CSV file of colours. You might not want to share the data (or the link to the data) on GitHub so you can email me at colin.combe@ed.ac.uk about how to proceed.

Its likely to be next week before I look at this,

cheers, Colin

xLinkKnight commented 2 years ago

I've attached the files. Thank you.

HemoglobinOnly_Script.csv Hb_ProteinOnly.txt

colin-combe commented 2 years ago

Hi,

If you rename the columns 'AbsPos1' and 'AbsPos2' to 'SeqPos 1' and 'SeqPos 2' in the file when you upload it as edge metadata (https://xiview.org/xidocs/html/import/crossmeta.html) then do you get the results you expect?

I realise this is a bit confusing - you have those columns named correctly for uploading our most minimal CSV format for crosslink data, but they're named differently when uploading link metadata.

I think you're using the same file as your data upload and your edge meta data - that should be fine I think. It would be better if xiVIEW read the metadata out of the CSV file and it was already there for you.

When the column names where wrong it was taking it as edge metadata at the PPI level which is why you got funny looking results.

Ask if further questions, cheers, Col

colin-combe commented 2 years ago

(with the edge metadata uploaded you should also be able to select "Quantitiation" from the Legend panel and have a range slider for controlling colours based on quantitation data)

xLinkKnight commented 2 years ago

That worked! It didn't occur to me that the column naming scheme might be different for the crosslink and metadata files.

crosslink column header: Protein1 | AbsPos1 | Protein2 | AbsPos2 | Score | Quantitation | Fixed Colour (last two columns are redundant)

metadata header: Protein 1 | SeqPos 1 | Protein 2 | SeqPos 2 | Quantitation | Fixed Colour

Thank you.

colin-combe commented 2 years ago

It didn't occur to me that the column naming scheme might be different for the crosslink and metadata files

yeah... it doesn't make a whole lot of sense now that i look at it