adding NLS to a peptide
0
0
Entering edit mode
7.0 years ago

i want to add signal peptide to a modelled protein how it can be added with bioinformatics?

signalling • 1.6k views
ADD COMMENT
0
Entering edit mode

Please be more verbose and precise about the methods and motivation of your question. What is the aim of this attempt, do you want to express a recombinant protein that is secreted, for example, or do you just want 'to see how it looks'? Where should the signal peptide be located? How did you 'model your protein'?

What is your expectation to the utility 'bioinformatics' other than editing and pasting the sequence in an editor?

ADD REPLY
0
Entering edit mode

i modeled a zinc finger for a specific location of dna . now i want to add a signal peptide to it .so that this modeled zinc finger will transported to nucleus . i need a computational method to do it. will i directly add the signal peptide sequence to the primary sequence of zinc finger or and then model it using geno3d or any other method is there?

ADD REPLY
0
Entering edit mode

Please use ADD COMMENT/ADD REPLY when responding to existing posts to keep threads logically organized.

ADD REPLY
0
Entering edit mode

You just want to create a fusion protein for expression? Or you want to do molecular dynamics computations on it? The 'bioinformatics' you'd need for these 2 tasks are not at all alike...

ADD REPLY
0
Entering edit mode

first i want to create a fusion protein which will be able to express . but i have designed a zinc finger in which i want to add NLS signal . i thought after making all these complex i will put it in some simulation server . but now i am confused what to do nest as i cant understand how to add a NLS peptide in that ZINC finger motif? and is it necessary to do molecular dynamic simulation of the fusion protein after modelling it.

ADD REPLY

Login before adding your answer.

Traffic: 1960 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6