Currently, the translateFeatures code does not allow for the creation of a new feature file that contains multiple features in one. (for example, I cannot translate the non-canonical merged file because there are SH2 domain NC contacts, kinasedom contacts, ptp_cat, etc that are listed as different features, so I have had to translate each feature set separately.
Describe the solution you'd like
Code creates a new feature file that includes multiple feature types so that other users do not have to separate their files by feature type. Similar to how the integrateFeatures function can handle multiple feature types.
Tasks
Include specific tasks in the order they need to be done in. Include links to specific lines of code where the task should happen at.
[ ] Modify code such that each new feature encountered is included in the feature list at the top of the feature file (as opposed to it only looking for the first entry in a line and encountering an error when there are more than one feature) and is assigned a color
[ ] Run the SH2_wt_merge file to generate one feature file containing all non-canonical contact types. This can also be checked with the all_PTMs feature file.
Currently, the translateFeatures code does not allow for the creation of a new feature file that contains multiple features in one. (for example, I cannot translate the non-canonical merged file because there are SH2 domain NC contacts, kinasedom contacts, ptp_cat, etc that are listed as different features, so I have had to translate each feature set separately.
Describe the solution you'd like Code creates a new feature file that includes multiple feature types so that other users do not have to separate their files by feature type. Similar to how the integrateFeatures function can handle multiple feature types.
Tasks
Include specific tasks in the order they need to be done in. Include links to specific lines of code where the task should happen at.