More at https://dahak-metagenomics.github.io/dahak/

Address of the bookmark: https://github.com/dahak-metagenomics/dahak

About Fellowship:
CSIR Nehru Science Postdoctoral Research Fellowship Scheme is an Research Fellowship awarded/given by HRD Ministry, Govt. of India every year to more than 100 fellows.

It was started to identify promising and young researchers with novel ideas and provide them research opportunities in the areas of basic science, engineering, medicine & agriculture.

The fellowship aims at facilitating their transition from mentored to independent research career.

In addition, check these ICTS Research Fellowships:
1.) Max-Planck Partner Group Fellowships 2017-18
2.) ICTS-Simons Postdoctoral Fellowships 2017
3.) ICTS Post Doctoral Fellowships 2017
4.) Airbus Prize Postdoctoral Fellowship 2017-18

Eligibility: To be eligible for this fellowship, you:
1.) PhD degree (within 3 years of award of PhD degree), OR
2.) Those who have submitted PhD theses.
3.) Applicants should have research publications in good impact factor SCI journals.
4.) Indian nationals, Persons of Indian Origin (PIO) & Overseas Citizen of India (OCI), a can also apply.
5.) Maximum Age Limit: 32 years.

Duration:
– 2 Years.
– extendable for a maximum of 1 more year based on performance.

Remuneration:
– Rs. 50,000/- per month plus House Rent Allowance (HRA)
– A contingency grant of Rs. 3.0 lakh per annum.
– 25% of the contingency grant can be used for domestic and international travel.

Mode of Selection: You can apply throughout the year, but selection will be made twice a year, in June and December.

How to Apply:
– Read the instructions, given at Annexure-I in this PDF file.
– And, application form is given as, Annexure-II.
– Fill the form & send it to the given address in the PDF file.

Deadline: Rolling Deadline (Applications accepted throughout the year)

Also See: Research Internship/ Fellowship in India:
1.) IIT Bombay Research Internship Awards Programme 2016-17
2.) IIT Delhi Internship Program 2016-17
3.) DAAD WISE – International Internship in Germany
4.) Summer Research Fellowship Programme| JNCASR Bangalore
5.) Indian Academy of Sciences Summer Internships 2017
6.) Winter Internship – IIT Bombay NPDE-TCA
7.) Viterbi – India Program 2017 | Research Internship in US
8.) Internship – Centre for Stem Cell Research, Vellore

Accommodation & other benefits:
– Accommodation may be provided by CSIR, if available.
– Medical benefits as per CSIR norms.

For more details:
– Check this PDF Notification of Fellowship.
– List of CSIR Labs & their work/activities can be seen at www.csir.res.in.

Address of the bookmark: http://www.ub.edu/dnasp/

Calls

Events

Projects

Jobs

Address of the bookmark: http://www.dbtindia.nic.in/out-reach/latest-announcements/

SYMPOSIUM DESCRIPTION: Genomics of Adaptation [S16] Model organisms for life-history research are mainly studied in the lab where functional genetics is assessable. In general, however, knowledge about their eco-evolutionary dynamics, such as biotic interactions, is rare. By contrast, in organisms for which the ecology and adaptation strategies in the field are well known, we typically lack the appropriate genetic tools to investigate functionality. Advances in genomics and statistics as well as investments in evolutionary model organisms are now providing access to putatively adaptive genome-wide variation within species from across the tree of life. In this symposium, we focus on integrating life-history biology, genetics and evolutionary ecology in the genomics era.

We wish to (1) highlight the role of genetic architecture of complex traits, such as adaptations to biotic interactions or life-history traits; (2) contrast this to morphological traits which are generally thought to have a less complex genetic architecture; and (3) discuss the opportunities and drawbacks of specific model systems.

INVITED SPEAKERS: Josephine Pemberton, University of Cambridge (http://bit.ly/2hJWytJ ) Peter Tiffin, University of Minnesota (http://bit.ly/2hK7HuS )

ABSTRACT SUBMISSION The deadline for abstract submission is January 10, 2017. For more information and to submit abstracts online, please visit: http://bit.ly/2fBXlvN We look forward to an exciting symposium and seeing you all in Groningen! Sincerely, Ben Blackman, UC Berkeley Maaike de Jong, University of Bristol Bart Pannebakker, Wageningen University Noah Whiteman, UC Berkeley Jelle Zandveld, Wageningen University

Mauve has been developed with the idea that a multiple genome aligner should require only modest computational resources. It employs algorithmic techniques that scale well in the lengths of sequences being aligned. For example, a pair of Y. pestis genomes can be aligned in under a minute, while a group of 9 divergent Enterobacterial genomes can be aligned in a few hours. However, the current algorithm’s compute time (progressiveMauve) scales cubically in the number of genomes to align, making it unsuitable for datasets containing more than 50-100 bacterial genomes.

Address of the bookmark: http://darlinglab.org/mauve/mauve.html

• Assembly of nanopore reads using Canu.
• Polish canu contigs using racon (optional).
• Map a paired-end Illumina dataset onto the contigs obtained in the previous steps using BWA mem.
• Perform correction of contigs using pilon and the Illumina dataset.

Address of the bookmark: https://github.com/nanoporetech/ont-assembly-polish

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

• dnaPipeTE is developped by Clément Goubert, Laurent Modolo and the TREEP team of the LBBE: http://lbbe.univ-lyon1.fr/-Equipe-Elements-transposables-.html?lang=en

• You can find the original publication in GBE here: https://academic.oup.com/gbe/article/7/4/1192/533768

output examples of quantification and TE landscape (relative age) produced by dnaPipeTE

Address of the bookmark: https://github.com/clemgoub/dnaPipeTE