PDB Chain: 2q9kA

Molscript image for 2q9kA
2q9kA
PDB coordinates for chain 2q9kA

PDB 2q9k, Chain A

CATH Domains (1)

Domain IDCATH codeImage
2q9kA00 2.30.110.10 Molscript image for 2q9kA00

Domain boundaries for PDB chain 2q9kA

Chain ATOM Sequence

>pdb|2q9kA
KVEHRLSEQQKALTDLPLVFLITHDQSKSWPITHAISWVYAKDETTIRFAIEADSLLVKTLADHPVFTLIFFADQSTYSL
TCTDVAAWETTARLPLKVALYEGQIKEVRDILFYGAAVSDRPRVYKTYDEAAAQLDQQIQDILKG    

Chain COMBS Sequence

>pdb|2q9kA
GXANKVEHRLSEQQXKALTDLPLVFLITHDQSKSWPITHAISWVYAKDETTIRFAIEADSLLVKTLADHPVFTLIFFADQ
STYSLTCTDVAAWETTARLPLKVALYEGQIKEVRDILFYGAAVSDRPRVYKTYDEAAAXQLDQQIQDILKG    

Chain History Events (63)

Flow stage update by cuff on 23 Aug 2007 14:44

nice chopping

Chain chopped by cuff on 23 Aug 2007 14:44

nice chopping

Chain chopping manual by rupa on 10 Aug 2007 12:52

wcd

Domchop review by rupa on 10 Aug 2007 12:52

wcd

Flow stage update by rupa on 10 Aug 2007 12:52

wcd

Domchop allotment by rupa on 10 Aug 2007 12:51

User 'rupa' has allocated a chain to themselves for DomChopping with comment : Grabbed this chain via DomChop's "Get Me A Chain" button.

Flow stage update by rupa on 10 Aug 2007 12:51

User 'rupa' has allocated a chain to themselves for DomChopping with comment : Grabbed this chain via DomChop's "Get Me A Chain" button.

Flow stage update by lewis on 06 Aug 2007 14:32

The HMM(SAM) scan for 2q9kA returned no results and this doesn't appear to be an error so I am shifting 2q9kA on to DOMCHOP_READY

Update comment by auto on 06 Aug 2007 11:05

HMM(SAM) job SID5267716171849248 for entry "2q9kA" returned no results. In an ideal world, all HMM(SAM) scans would return results. This isn't an ideal world and we're all going to have to deal with that. You need to decide why this HMM(SAM) scan has returned no results. Is it because there are no good HMM hits or is it because something has gone wrong? SG structures are more likely to have no decent HMM(SAM) hits than normal structures.

If something has gone wrong, please track down the problem and fix it.

If you are happy that there is no problem, then you may wish to run a command like the following one:

/usr/local/svn/source/update/v3.1.1/utilities/UpdateFlowStage.pl -d cathdb_current -h fletcher -u -p -f HMM_GATHER -t DOMCHOP_READY -i 2q9kA -m "The HMM(SAM) scan for 2q9kA returned no results and this doesn't appear to be an error so I am shifting 2q9kA on to DOMCHOP_READY"

Update comment by auto on 06 Aug 2007 08:53

HMM(SAM) job SID5267716171849248 is not yet finished.

Hmm submit by auto on 06 Aug 2007 06:39

The entry "2q9kA" has been submitted to the HMM (SAM) webservice.

Flow stage update by auto on 06 Aug 2007 06:39

The entry "2q9kA" has been submitted to the HMM (SAM) webservice.

Flow stage update by auto on 06 Aug 2007 06:28

Retrieved "2q9kA" CATHEDRAL results for job ID SID5449805545666428 and inserted them into the database.

Chain chopping cathedral by auto on 06 Aug 2007 06:28

Chain "2q9kA" CATHEDRAL chopping from job SID5449805545666428

Update comment by auto on 05 Aug 2007 17:43

"2q9kA" CATHEDRAL job SID5449805545666428 is not yet finished.

Cathedral submit by auto on 05 Aug 2007 15:54

The entry "2q9kA" has been submitted to the CATHEDRAL webservice.

Flow stage update by auto on 05 Aug 2007 15:54

The entry "2q9kA" has been submitted to the CATHEDRAL webservice.

Flow stage update by auto on 05 Aug 2007 11:52

ScanList with 9616 domains written to "/cath/data/current/scanlists/cathdb_current.fletcher/2q9kA.scanlist" for "2q9kA"

Update comment by auto on 05 Aug 2007 06:49

Waiting for 2895 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 05 Aug 2007 02:43

Waiting for 2937 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 04 Aug 2007 22:28

Waiting for 2979 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 04 Aug 2007 18:36

Waiting for 3049 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 04 Aug 2007 14:38

Waiting for 3117 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 04 Aug 2007 10:38

Waiting for 3173 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 04 Aug 2007 06:32

Waiting for 3227 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 04 Aug 2007 02:41

Waiting for 3254 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 03 Aug 2007 22:32

Waiting for 3261 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 03 Aug 2007 19:22

Waiting for 3262 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 03 Aug 2007 15:13

Waiting for 3306 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 03 Aug 2007 10:28

Waiting for 3126 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 03 Aug 2007 06:31

Waiting for 3204 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 03 Aug 2007 02:31

Waiting for 3254 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 02 Aug 2007 22:23

Waiting for 3282 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 02 Aug 2007 18:56

Waiting for 3339 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 02 Aug 2007 14:47

Waiting for 3395 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 02 Aug 2007 10:28

Waiting for 3471 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 02 Aug 2007 06:29

Waiting for 3542 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 02 Aug 2007 02:30

Waiting for 3606 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 01 Aug 2007 22:19

Waiting for 3650 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 01 Aug 2007 18:57

Waiting for 3730 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 01 Aug 2007 14:29

Waiting for 3801 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 01 Aug 2007 10:19

Waiting for 3885 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 01 Aug 2007 06:23

Waiting for 3940 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 01 Aug 2007 02:26

Waiting for 3998 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 31 Jul 2007 22:14

Waiting for 4079 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 31 Jul 2007 18:31

Waiting for 4169 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 31 Jul 2007 14:25

Waiting for 4236 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Update comment by auto on 31 Jul 2007 10:13

Waiting for 4310 new domains (example : 1gviA01) to be processed so that they can be scanned against too.

Chain chopping domak by auto on 31 Jul 2007 10:10

Chopping proposed by the "CHAIN_CHOPPING_DOMAK" algorithm

Chain chopping detective by auto on 31 Jul 2007 10:10

Chopping proposed by the "CHAIN_CHOPPING_DETECTIVE" algorithm

Chain chopping puu by auto on 31 Jul 2007 10:10

Chopping proposed by the "CHAIN_CHOPPING_PUU" algorithm

Flow stage update by auto on 31 Jul 2007 10:10

Added putative Choppings from the DBS that ran (CHAIN_CHOPPING_DETECTIVE, CHAIN_CHOPPING_DOMAK, CHAIN_CHOPPING_PUU) for Chain "2q9kA"

Flow stage update by auto on 31 Jul 2007 10:08

Number of chains in ballcock flow stages is 799 which is less than the max allowed of 800

Update comment by auto on 28 Jul 2007 22:19

Number of chains in ballcock flow stages is 800 which hits the the max allowed of 800

Update comment by auto on 13 Jul 2007 16:24

Number of chains in ballcock flow stages is 400 which hits the the max allowed of 400

Flow stage update by auto on 13 Jul 2007 16:09

ChopClose result is not good enough for automatic chopping

Chain chopping chopclose by auto on 13 Jul 2007 16:09

Putative ChopClose added based on similarity with "1qb3B"

Flow stage update by auto on 12 Jul 2007 20:51

No in_process hits for Chain "2q9kA" ready to be processed

Flow stage update by auto on 12 Jul 2007 20:37

NW result present for Chain "2q9kA"

Flow stage update by auto on 12 Jul 2007 20:30

All required files are present for Chain "2q9kA"

Flow stage update by auto on 12 Jul 2007 20:04

Beginning processing for Chain "2q9kA"

Flow stage update by auto on 21 Jun 2007 18:44

Chain passed the SIFT criteria

Insertion by auto on 21 Jun 2007 18:43

Adding chain from chain pdb dir "/cath/data/current/chainpdb"