More at http://www.du.ac.in/du/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=12859&cntnt01returnid=83

http://www.boseinst.ernet.in/advertisement.html

THIRUVANANTHAPURAM - 695 562

Traineeship on Bioinformatics(2)

First class M.Sc. Bioinformatics/ Agriculture/ Botany/ Biotechnology @ Rs.8000

Those candidates who fulfill the above criteria may attend a walk PCC Coordinator in-interview on 28th November 2016 at Saraswathy Thangavelu center, JNTBGRI, Puthenthope, Thiruvananthapuram between at 10.00 am and 2.00 pm with all the relevant document and testimonials.

No TA/DA will be given to candidates for attending the interview.

More Info : http://jntbgri.res.in/downloads/traineeship_notification.pdf

Research Associate :
Essential Qualification: Ph.D in Bioinformatics/Biotechnology/Life Science from a reocngised univeristy/institute
Pay: Rs.36000-/- + Admissible 10% HRA per month
Age: Below 35 years

Junior Research Fellow
Essential Qualification: M.Sc in Bioinformatics/Biotechnology/Life Science from a reocngised univeristy/institute
Pay: Rs.18000-/- + per month
Age: Below 35 years

Last date for receving application by mail or post is 08.11.2016

Company Info.
North-Eastern Hill University

Bioinformatics Infrastructure Facility (BIF) Department of RDAP North-Eastern Hill University, Tura Campus Tura-794002, Meghalaya

More at http://www.nehu.ac.in/Advertisements/BIFTuraManpowerAdvt_25102016.pdf

Position (scale), qualifications and experience

1. Information Officer (Rs 8000-275-13500): one post
Qualifications and experience: MCA, Post-Graduate in any field of biosciences, bioinformatics with at least two years of experience in working in a bioinformatics setup and good knowledge of linux operating system and computer networking.

General terms and conditions:
1. The above engagements is presently till March 31st, 2017. However on extension of project grant and satisfactory performance of the candidate, your services can be extended beyond March 31st, 2017 based on the terms and conditions of extension of project grant.

2. It is not an appointment with the institute and will not confer any right to the incumbent to any claim implicit or explicit on any position.

3.No TA/DA will be paid for attending the interview. Outstation candidates have to make their own arrangement for their stay.

4.Candidates, appearing in the walk-in interview are requested to bring the hard copy of application addressed to Dr. Anju Pappachan with latest photograph, CV mentioning qualifications, work experience and name of two referees and one page write up as to why you would like to join the project.

Address:
Dr. Anju Pappachan
Indian Institute of Advanced Research (IIAR),
University and Institute of Advanced Research,
The Puri Foundation for Education in India,
Koba Institutional Area,
Gandhinagar- 382 007, Gujarat, India. Contact no. 079-30514152
e-mail- anju@iiar.res.in

Noida 201301 (U.P)

Applications are invited upto 21.11.2016 from interested candidates as per details available on NICPR website (www.nicpr.res.in)/ ICMR website (www.icmr.nic.in) to fill up following temporary position in the time bound DHR Project entitled “Next generation EGFR inhibitor identification using ligand based QSAR technique” under Dr. Subhash M. Agarwal, Scientist-D, Division of Bioinformatics.

Research Assistant (One)

Rs.27000/- p.m. (Fixed/temporary)

Essential: M.Sc. in Bioinformatics or related field.

Desirable: Experience in QSAR and structure based drug designing.

More Info : www.icmr.nic.in/icmrnews/NICPR_Advertisement%20for%20RA.pdf

More at
https://zfin.org/ZDB-LAB-110408-1
http://www.imcb.a-star.edu.sg/php/venkatesh.php

Address of the bookmark: http://engr.case.edu/li_jing/papers/00798gpattern.pdf

In C, "sequence statements" are imperatives. The "selection" is the "if then else" statement, and the iteration is satisfied by a number of statements, such as the "while," " do," and the "for," while the case-type statement is satisfied by the "switch" statement.

Pseudocode is an artificial and informal language that helps programmers develop algorithms. Pseudocode is a "text-based" detail (algorithmic) design tool.

The rules of Pseudocode are reasonably straightforward. All statements showing "dependency" are to be indented. These include while, do, for, if, switch. Examples below will illustrate this notion.

GUIDE TO PSEUDOCODE LEVEL OF DETAIL: Given record/file descriptions, pseudocode should be created in sufficient detail so as to directly support the programming effort. It is the purpose of pseudocode to elaborate on the algorithmic detail and not just cite an abstraction.

Examples:

1.

If student's grade is greater than or equal to 60
    Print "passed"
else
    Print "failed"  
endif

2.

  
Set total to zero
Set grade counter to one
While grade counter is less than or equal to ten
    Input the next grade
    Add the grade into the total
endwhile 
Set the class average to the total divided by ten
Print the class average.

3.

Initialize total to zero
Initialize counter to zero
Input the first grade
while the user has not as yet entered the sentinel
   add this grade into the running total 
   add one to the grade counter  
   input the next grade (possibly the sentinel)
endwhile

if the counter is not equal to zero
   set the average to the total divided by the counter
   print the average  
else
   print 'no grades were entered' 
endif 

4.

initialize passes to zero
initialize failures to zero
initialize student to one
while student counter is less than or equal to ten
    input the next exam result  
    if the student passed

add one to passes else add one to failures add one to student counter endif endwhile print the number of passes print the number of failures if eight or more students passed print "raise tuition" endif

5.

Larger example:  

NOTE:  NEVER ANY DATA DECLARATIONS IN PSEUDOCODE

Print out appropriate heading and make it pretty
While not EOF do:
     Scan over blanks and white space until a char is found 
	(get first character on the line)
     set can't-be-ascending-flag to 0
     set consec cntr to 1
     set ascending cntr to 1
     putchar first char of string to screen
     set read character to hold character
     While next character read != blanks and white space
          putchar out on screen
          if new char = hold char + 1
               add 1 to consec cntr
               set hold char = new char
               continue
          endif
          if new char >= hold char 
               if consec cntr < 3 
                    set consec cntr to 1
               endif
               set hold char = new char
               continue
          endif
          if new char < hold char
               if consec cntr < 3
                    set consec cntr to 1
               endif
               set hold char = new char
               set can't be ascending flag to 1
               continue
           endif
     end while
     if consec cntr >= 3 
          printf (Appropriate message 1 and skip a line)
          add 1 to consec total
     endif
     if  can't be ascending flag = 0
          printf (Appropriate message 2 and skip a line)
          add 1 to ascending total
     else
          printf (Sorry message and skip a line)
          add 1 to sorry total
     endif
end While
Print out totals:  Number of consecs, ascendings, and sorries.
Stop

Some Keywords That Should be Used And Additional Points

For looping and selection, The keywords that are to be used include Do While...EndDo; Do Until...Enddo; While .... Endwhile is acceptable. Also, Loop .... endloop is also VERY good and is language independent. Case...EndCase; If...Endif; Call ... with (parameters); Call; Return ....; Return; When;

Always use scope terminators for loops and iteration.

As verbs, use the words Generate, Compute, Process, etc. Words such as set, reset, increment, compute, calculate, add, sum, multiply, ... print, display, input, output, edit, test , etc. with careful indentation tend to foster desirable pseudocode. Also, using words such as Set and Initialize, when assigning values to variables is also desirable.

More on Formatting and Conventions in Pseudocoding

• INDENTATION in pseudocode should be identical to its implementation in a programming language. Try to indent at least four spaces.
• As noted above, the pseudocode entries are to be cryptic, AND SHOULD NOT BE PROSE. NO SENTENCES.
• No flower boxes (discussed ahead) in your pseudocode.
• Do not include data declarations in your pseudocode.
• But do cite variables that are initialized as part of their declarations. E.g. "initialize count to zero" is a good entry.

  ---

  Function Calls, Function Documentation, and Pseudocode
• Calls to Functions should appear as:
• Returns in functions should appear as:
• Function headers should appear as:
• Note that in C, arguments and parameters such as "fieldn" could be written: "pointer to fieldn ...."
• Functions called with addresses should be written as:
• Function headers containing pointers should be indicated as:
• Returns in functions where a pointer is returned:
• It would not hurt the appearance of your pseudocode to draw a line or make your function header line "bold" in your pseudocode. Try to set off your functions.
• Try to use scope terminators in your pseudocode and source code too. It really hels the readability of the text.

  ---

  Source Code
• EVERY function should have a flowerbox PRECEDING IT. This flower box is to include the functions name, the main purpose of the function, parameters it is expecting (number and type), and the type of the data it returns. All of these listed items are to be on separate lines with spaces in between each explanatory item.
• FORMAT of flowerbox should be

   

  	 ********************************************************
  	 Function:   ( cryptic text describing single function
  		     ....... (indented like this) 	
  		     .......
  	 Calls:      Start listing functions "this" function calls
  		     Show these functions:  one per line, indented
  
  	 Called by:  List of functions that calls "this" function
  		     Show these functions:  one per line, indented.
  
  	 Input Parameters:  list, if appropriate; else None
  	 
  	 Returns:    List, if appropriate.
  	 ****************************************************************
  

• INDENTATION is critically important in Source Code. Follow standard examples given in class. If in doubt, ASK. Always indent statements within IFs, FOR loops, WILLE loops, SWITCH statements, etc. a consistent number of spaces, such as four. Alternatively, use the tab key. One or two spaces is insufficient.
• Use scope terminators at the end of if statements, for statements, while statements, and at the end of functions. It will make your program much more readable.

  SPELLING ERRORS ARE NOT ACCEPTABLE

Upcoming Deadlines
Regular Paper Submission: July 31, 2017
Regular Paper Authors Notification: October 16, 2017
Regular Paper Camera Ready and Registration: October 30, 2017

The purpose of the International Conference on Bioinformatics Models, Methods and Algorithms is to bring together researchers and practitioners interested in the application of computational systems, algorithmic concepts and information technologies to address challenging problems in Biomedical research with a particular focus on the emerging problems in Bioinformatics and computational biology. There is a tremendous need to explore how mathematical, statistical and computational models can be used to better understand biological processes and systems, while developing new methodologies and tools to analysis the massive currently-available biological data. Areas of interest to this community include systems biology, sequence analysis, biostatistics, image analysis, network and graph models, scientific data management and data mining, machine learning, pattern recognition, computational evolutionary biology, computational genomics and proteomics, and related areas.