Address of the bookmark: https://sourceforge.net/projects/excavator2tool/

Advertisement for Faculty Positions

The IISER Berhampur, an Institute of national importance, established through an act of Parliament is an autonomous organization under the Ministry of HRD, Govt. of India, to promote quality education and cutting edge research in basic sciences and to provide a platform for the faculty to engage in high quality education, at undergraduate and postgraduate levels. The Institute invites applications for faculty positions at the level of Assistant Professor (C) /Assistant Professor in the following disciplines:

1. Biological Sciences

2. Chemistry

3. Computer Sciences

4. Mathematics

5. Physics

Only hard copy of application in the prescribed format, via Speed Post should be sent to the Dean, Faculty Affairs, IISER Berhampur, Industrial Training Institute (ITI) Berhampur, Engineering School Road, Berhampur - 760 010, Ganjam District, Odisha, before 1700 hrs., December 30, 2016.

http://www.iiserbpr.ac.in

More Info : http://www.iiserbpr.ac.in/vacancies/Advertisement%20for%20Faculty%20Positions%20at%20IISER%20Berhampur.pdf

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

Pondicherry University, Puducherry has been identified as a nodal agency by the Department of Biotechnology, Govt. of India to coordinate this examination along with nine centres namely,

Pune University, Pune;

Anna University, Chennai;

Bose Institute, Kolkata;

Institute of Bioinformatics & Applied Biotechnology, Bangalore;

North-Eastern Hill University, Shillong, University of Hyderabad, Hyderabad;

University of Kerala, Thiruvananthapuram;

Jawaharlal Nehru University, New Delhi and

Assam Agricultural University, Guwahati. 

In the BINC 2015 and 2016 examination, 23 candidates and five candidates were certified respectively. DBT has agreed to fund Research fellowships for all the BINC qualified Indian nationals to pursue Ph.D. in Indian Institutes/Universities.

Note that the candidate must possess a postgraduate degree(or equivalent) & meet the criteria of the institutes/universities in order to avail research fellowship.

In addition, cash prize of Rs. 10,000/- will be awarded to the top 10 BINC qualifiers.

More at http://www.pondiuni.edu.in/exams/binc/

Candidates interested in the position should contact me in advance by email to: g.stracquadanio@essex.ac.uk

The deadline for the application is 28/02/2017; info about the application can be found on the Essex CSEE website.

With advances in Cancer Genomics, Mutation Annotation Format (MAF) is being widley accepted and used to store variants detected. The Cancer Genome Atlas Project has seqenced over 30 different cancers with sample size of each cancer type being over 200. The resulting data consisting of genetic variants is stored in the form of Mutation Annotation Format. This package attempts to summarize, analyze, annotate and visualize MAF files in an efficient manner either from TCGA sources or any in-house studies as long as the data is in MAF format. Maftools can also handle ICGC Simple Somatic Mutation format.

maftools is on bioRxiv

Please cite the below if you find this tool useful for you.

Mayakonda, A. and H.P. Koeffler, Maftools: Efficient analysis, visualization and summarization of MAF files from large-scale cohort based cancer studies. bioRxiv, 2016. doi: http://dx.doi.org/10.1101/052662

Address of the bookmark: https://github.com/PoisonAlien/maftools

• optimized to work with vast amount of data and very large file sets (~ 10,000 - 100,000).
• allows the selective retrieval of only the required files (file masks, ls-lR parsing, recursive search, updates)
• has a built-in repository containing the settings for the most common bioinformatics download needs
• built-in wizard for batch post-processing of downloaded files (archive extraction, file conversion, etc.)
• capable of performing multiple download or update tasks simultaneously

BioDownloader has a built-in repository containing the settings for common bioinformatics file-synchronization needs, including the Protein Data Bank (PDB) and National Center for Biotechnology Information (NCBI) databases. It can post-process downloaded files, including archive extraction and file conversions.

http://dunbrack.fccc.edu/BioDownloader/

Address of the bookmark: http://dunbrack.fccc.edu/BioDownloader/

This software distribution includes both the DAGchainer utility and a Java-based graphical interface that allows the inputs and outputs to be navigated and interrogated dynamically.

Address of the bookmark: http://dagchainer.sourceforge.net/

Reference: http://www.unitedformedicalresearch.com/wp-content/uploads/2013/06/The-Impact-of-Genomics-on-the-US-Economy.pdf