RA / Research Associate (Bioinformatics/Computational Biologist)
Salary: Rs. 23000/- + HRA
Vacancy: 1
Essential Qualifications: PhD, preferably in plant biotechnology/biochemistry/Bioinformatics with experience in analyzing high throughput omics-based data. Desired Skills: Prior experience in handling and guiding bioinformatics, metabolomics data, managing the project portal, preparing and filing reports etc. Will be expected to communicate with user groups and coordinate with LIMS group in Hyderabad and the Cheminformatics group in Delhi.

Address: Prof Indira Ghosh, room #12 Project Investigator, (Core Metabolomics) School of Computational and Integrative Sciences, Jawaharlal Nehru University, New Delhi-110 067.

Apply Details
Last Date: March 3rd 2015
Web/Notification URL http://www.jnu.ac.in/Career/currentjobs. htm

Starting with your current or most recent employment provide details of your position as follows:

• A chronological CV should be arranged in reverse chronological order. It should be apparent immediately where you are now.
• Remember that an application form is limited to the few things that a particular institution wants to know about everybody. A CV lets you give information that is unique to you. Add all your key accomplishments and activities in the initial draft. In subsequent drafts, you can remove information that may not be pertinent.
• Resist the temptation to append explanatory sentences or language, which will distract the reader from the basic information being presented. The language of a CV is abbreviated and succinct. When applying for residency training, you will have the opportunity to express yourself in a personal or biographical statement. In the future, when applying for a job or some other type of position, you will want to include an appropriate cover letter with your CV to explain your particular qualifications and strengths for the position.
• Don’t despair if your CV doesn’t resemble those of other students who are applying to the same residency program. Everybody’s CV is different. Even if everyone used the same format suggested in this section, your CV will not resemble others’ because it doesn’t have the same content. No residency program director is looking for a specific CV style. You will receive points for neatness, and readability.
• Be honest. If you haven’t accomplished anything in a particular category, leave it out. Don’t create accomplishments to fill in the spaces. You can be specific about your level of participation in a project or activity, but don’t be misleading (i.e., you can say you coordinated membership recruitment for your AMSA chapter, but don’t say you were “president” unless you were).

• Job title - time that you have held this position
• The key tasks and responsibilities that comprise this role's requirements - notable achievements whilst in the role
• Where possible quantify your achievements with precise facts and figures, e.g. managed junior staff, handled department budget, prepared management reports
• Expand on the skills you are using in your current job which you believe will be valuable in the position(s) for which you are applying

It is not necessary to state the reason you are leaving your current position. This will be a topic for conversation when you are invited for interview or can be covered in your letter of application.
For all previous employment, unless one appointment was more significant than your current or last position, keep details brief i.e. the name of the company, job title, period of employment and the job.
Be sure there are no gaps in your career history - unless for example you took a year out to travel, in which case make reference to this under Interests/Hobbies.
If you are a student just starting work, give any evidence you can to demonstrate your practical skills e.g. school prefect, event organisation, member of sports team, contributor to college magazine or voluntary work.

You are under no obligation to disclose marital status, age or whether or not you have children unless these are specific criteria for selection for a position that you are interested in.
Consider what examples (interests/ hobbies) you can give to show that you match the selection criteria.

If they want someone to work as part of a large team, remember to say if you belong to a local organisation or if you are part of a sports team.

If they want someone who will work on their own for large periods of time, make reference to an Open University course you are considering undertaking.

Your primary objective is to convince the prospective employer that you have the requisite skills, experience and hunger to do the job.

Your CV should be no more than two A4 pages and as every employer is different remember to customise your CV to every job you go after.

There are abundant books on the contents and presentation of a general CV. A BMJ article published in 1978, offering doctors guidance on how to prepare a CV, has been reprinted in the widely read How to do it series.1 2 A survey among postgraduate deans and training advisers at regional colleges found that the contents and presentation of a model CV for doctors in training has been published.3 It is perhaps surprising to note that these models differ significantly from one another. Although they may be useful as starting points, their differences tend to create confusion and anxiety among students. I would argue that these differences exist because the content and presentation of the "ideal" CV vary considerably among individual applicants, the stage of their careers, and the purposes for which the CV is used. It is impossible to create a generic CV. I have therefore not attempted to draw up another model CV. Rather, the purpose of this article is to outline the general principles and important practical points in preparing a good CV. General principles on contents Before finalising your CV for a particular purpose you must be sure of your objectives, whether it is used as an initial screening or the only selection instrument, and the criteria against which it is judged. What details, and how many of them, to include in your CV depends on these factors. I shall illustrate with examples relevant to medical students. 

(1) Job application Your objective is to get the job. In a job application, the CV is used for two purposes: as an initial screening instrument for shortlisting candidates and as a framework for discussion during the interview. The explicit criteria used for shortlisting are usually given in the job advertisement. For some organisations, separate lists of essential and desirable criteria are given. Alternatively, you can get a good idea of the basic requirements from the job description. Your CV must clearly highlight these criteria, preferably on the first page. These usually include: formal qualifications; registration with the General Medical Council; and the prescribed experience. It is sometimes easy to forget to mention items specifically asked for in the job description (for example, a valid driving licence). The implicit criteria are less easy to pinpoint. For example, how much detail on your BSc dissertation and publications should you include? Should you make a long list of extracurricular activities, interests outside medicine, and positions of responsibility? If you admit to a wide range of extracurricular activities and interests, would you be considered as a candidate with a well balanced mature personality or will it be interpreted to mean that you will have little time or interest to do your job? There are no easy answers. Common sense might tell you that BSc dissertation and publications are more important in application for teaching hospital or research posts, but less important for district hospital posts. Conversely, you might think that interests outside medicine are more important for posts in district hospitals or in general practice. This is, however, not always true. A few consultants at district hospital are highly academic. Information gathered from students and doctors working under the professor or consultant concerned may be vital. Alternatively, it is worth while doing your homework by looking up your prospective consultant in the medical directory. This may occasionally prompt you to include information that you might otherwise have left out. For example, you may find that the consultant qualified in Scotland and has previously worked in Scotland for a considerable time, and you may decide to add in your CV that you studied in a Scottish secondary school. Since the CV is only used as for initial screening, you need not go into your previous experience or extracurricular activities in too much detail. Highlight only the most significant points, and leave the details for the interview. If you are applying for a clinical post, one of your referees should be a consultant for whom you have worked as a student. You should ask for permission to use his/her name before submitting your application. 

(2) Application for research scholarship or PhD studentship The CV and application form are sometimes used as the sole selection instrument, and you must make enquiries before you submit your application. Clearly, academic ability is the main criterion for selection, and you should include as much information relevant to your academic ability and interests as you can. Examples are your A levels, your BSc dissertation, any publications (even in the form of a letter in newspaper), any experience as an editor (for example, for your school magazine). Your extracurricular activities are less important, and you can simply give a short list. At least one of the referees should be an academic - for example, your previous supervisor in your BSc degree.
 
(3) Application to join a clinical course in another medical school Preclinical students who have completed an intercalated degree often have the option of applying to join a clinical course in another medical school, although it may become more difficult to do so with the introduction of the new GMC curriculum. Your CV is usually used for shortlisting candidates for interview. The criteria differ slightly among medical schools, but both academic ability and contribution to university life are important. Hence, not only should you highlight your academic achievements but you must also highlight your participation in the university (for example, in sports or music). 

(4) For the information of your tutor or counsellor For most medical schools, you are allocated a tutor who provides both academic and non-academic support and monitors your progress throughout your study on a confidential basis. Students are sometimes asked to submit their up to date CV to their tutors for information. Assuming that the tutors are helpful there is little to gain from over emphasising your strengths or hiding your weaknesses. Once you become a doctor in training after you qualify you will need to undergo an annual assessment of your progress. It serves to certify that you have reached a satisfactory standard, but it is also used as an aid to identify and help with your weaknesses. You may find it difficult to balance these two purposes in presenting your CV. General principles on presentation Now that all students are computer literate, there should be few problems in preparing a well presented CV. The following list serves as a reminder on how to present your CV effectively: Spelling or grammar mistakes - do not rely purely on the spell check on your computer. Ask friends to proofread your CV for you. Consistency - The use of punctuation to open and close sentences, justification, and fonts should be consistent. Readability - The headings should be clear. The font size should be no less than 12 point. Basic criteria - The basic criteria should be easily located, preferably on the first page. Length - The length of your CV increases as you progress up the professional ladder. For students, it should generally be no more than three pages. Quality of print - The CV should be printed on good quality paper, preferably using a laser printer. Practical points In this article, I argue that different versions of a CV may be required for different purposes. Even applications for different posts in the same specialty may require slightly different versions. Also, CVs need to be updated regularly. This would have been time consuming to achieve in the past, but it is now quite simple, with the aid of a basic word processing package. A master CV containing all relevant information should be prepared and saved as a computer file. This should be continuously kept up to date. When the need for a CV arises, it can be tailormade by editing the master document. It is important to save each of these edited versions separately, with the file names indicating the date when it was created and the purpose. It is also important to prepare a cover letter to go with the CV. Key messages A good CV is essential for successful progression up the medical professional ladder The contents of the CV should be tailormade for the purpose it is used for and the criteria against which it is judged. It is important to gather information about these criteria first The CV must be technically well presented, with the basic criteria easily located Information technology has made it simple to regularly update our CVs and allows preparation of different versions of a CV for different purposes with relative ease.

Reference:

Prepare a curriculum vitae. BMJ 1978;25(2):1478-9.
O'Brien E. Prepare a curriculum vitae. In: Reece D, ed. 
How to do it. Vol 1. London: BMJ Publishing Group, 1995 Chambler AF, Chapman-Sheath PJ, Pearse MF. 
A model curriculum vitae: what are the trainers looking for? Hosp Med 1998;59(4):324-6.

R-language: http://www.r-project.org

BioConductor: http://www.bioconductor.org

Advantages of R

• Free!
• Powerful, many libraries have been created to perform application specific tasks. e.g. analysis of microarray experiments and Next-Gen sequencing (bioconductor: including Bioseq group).
• Presentation quality graphics
  • Save as a png, pdf or svg
• History
  • What you do can be saved for the next time you use R.
  • Ability to turn it into an automated script to perform again and again on different data

Disadvantages

• Lack of a comprehensive graphical user interface, but two do exist: However some do exist: R commander: http://socserv.mcmaster.ca/jfox/Misc/Rcmdr/ and Limma-gui (microarrays) : http://bioinf.wehi.edu.au/limmaGUI/

Preparation

• (Optional) Download and save the tutorial data set from
  • http://bioinformatics.knowledgeblog.org/wp-content/uploads/bioinf/kerr/data.tsv
  • Start R (type R on a Linux or Mac terminal, or find the starting link from PC)

Getting More Help

• Project Home page
  • http://www.r-project.org/
  • Check out the ‘introduction to R’, which is a much more in depth guide .
  • Also R has a built-in help system (see later)

Working directory

This is the directory used to store your data and results. It is useful if it is also the directory where your input data is stored.

• Mac/Linux: this is the directory where you typed in R
• PC: Change using the change working directory option

Upgrading to R 3.2.0 on Windows

If you are using Windows you can easily upgrade to the latest version of R using the installr package. Simply run the following code:

# installing/loading the latest installr package:
install.packages("installr"); library(installr) #load / install+load installr
 
updateR() # updating R.

Running “updateR()” will detect if there is a new R version available, and if so it will download+install it (etc.).

If you are an R blogger yourself you are invited to add your own R content feed to this site (Non-English R bloggers should add themselves- here)

NEW FEATURES

• anyNA() gains a recursive argument.
• When x is missing and names is not false (including the default value), Sys.getenv(x, names) returns an object of class "Dlist" and hence prints tidily.
• (Windows.) shell() no longer consults the environment variable SHELL: too many systems have been encountered where it was set incorrectly (usually to a path where software was compiled, not where it was installed). R_SHELL, the preferred way to select a non-default shell, can be used instead.
• Some unusual arguments to embedFonts() can now be specified as character vectors, and the defaults have been changed accordingly.
• Functions in the Summary group duplicate less. (PR#15798)
• (Unix-alikes.) system(cmd, input = ) now uses ‘shell-execution-environment’ redirection, which will be more natural if cmd is not a single command (but requires a POSIX-compliant shell). (Wish of PR#15508)
• read.fwf() and read.DIF() gain a fileEncoding argument, for convenience.
• Graphics devices can add attributes to their description in .Device and .Devices. Several of those included with R use a "filepath" attribute.
• pmatch() uses hashing in more cases and so is faster at the expense of using more memory. (PR#15697)
• pairs() gains new arguments to select sets of variables to be plotted against each other.
• file.info(, extra_cols = FALSE) allows a minimal set of columns to be computed on Unix-alikes: on some systems without properly-configured caching this can be significantly faster with large file lists.
• New function dir.exists() in package base to test efficiently whether one or more paths exist and are directories.
• dput() and friends gain new controls hexNumeric and digits17 which output double and complex quantities as, respectively, binary fractions (exactly, see sprintf("%a")) and as decimals with up to 17 significant digits.
• save(), saveRDS() and serialize() now support ascii = NA which writes ASCII files using sprintf("%a") for double/complex quantities. This is read-compatible with ascii = TRUE but avoids binary->decimal->binary conversions with potential loss of precision. Unfortunately the Windows C runtime’s lack of C99 compliance means that the format cannot be read correctly there in R before 3.1.2.
• The default for formatC(decimal.mark =) has been changed to be getOption("OutDec"); this makes it more consistent with format() and suitable for use in print methods, e.g. those for classes "density", "ecdf", "stepfun" and "summary.lm".

  getOption("OutDec") is now consulted by the print method for class "kmeans", by cut(), dendrogram(), plot.ts() and quantile() when constructing labels and for the report fromlegend(trace = TRUE).

  (In part, wish of PR#15819.)

• printNum() and hence format() and formatC() give a warning if big.mark and decimal.mark are set to the same value (period and comma are not uncommonly used for each, and this is a check that conventions have not got mixed).
• merge() can create a result which uses long vectors on 64-bit platforms.
• dget() gains a new argument keep.source which defaults to FALSE for speed (dput() and dget() are most often used for data objects where this can make dget() many times faster).
• Packages may now use a file of common macro definitions in their help files, and may import definitions from other packages.
• A number of macros have been added in the new ‘share/Rd’ directory for use in package overview help pages, and promptPackage() now makes use of them.
• tools::parse_Rd() gains a new permissive argument which converts unrecognized macros into text. This is used by utils:::format.bibentry to allow LaTeX markup to be ignored.
• options(OutDec =) can now specify a multi-byte character, e.g., options(OutDec = "u00b7") in a UTF-8 locale.
• is.recursive(x) is no longer true when x is an external pointer, a weak reference or byte code; the first enables all.equal(x, x) when x .
• ls() (aka objects()) and as.list.environment() gain a new argument sorted.
• The "source" attribute (which has not been added to functions by R since before R version 2.14.0) is no longer treated as special.
• Function returnValue() has been added to give on.exit() code access to a function’s return value for debugging purposes.
• crossprod(x, y) allows more matrix coercions when x or y are vectors, now equalling t(x) %*% y in these cases (also reported by Radford Neal). Similarly, tcrossprod(x,y) and %*% work in more cases with vector arguments.
• Utility function dynGet() useful for detecting cycles, aka infinite recursions.
• The byte-code compiler and interpreter include new instructions that allow many scalar subsetting and assignment and scalar arithmetic operations to be handled more efficiently. This can result in significant performance improvements in scalar numerical code.
• apply(m, 2, identity) is now the same as the matrix m when it has named row names.
• A new function debuggingState() has been added, allowing to temporarily turn off debugging.
• example() gets a new optional argument run.donttest and tools::Rd2ex() a corresponding commentDonttest, with a default such that example(..) in help examples will run donttest code only if used interactively (a change in behaviour).
• rbind.data.frame() gains an optional argument make.row.names, for potential speedup.
• New function extSoftVersion() to report on the versions of third-party software in use in this session. Currently reports versions of zlib, bzlib, the liblzma from xz, PCRE, ICU, TRE and the iconv implementation.

  A similar function grSoftVersion() in package grDevices reports on third-party graphics software.

  Function tcltk::tclVersion() reports the Tcl/Tk version.

• Calling callGeneric() without arguments now works with primitive generics to some extent.
• vapply(x, FUN, FUN.VALUE) is more efficient notably for large length(FUN.VALUE); as extension of PR#16061.
• as.table() now allows tables with one or more dimensions of length 0 (such as as.table(integer())).
• names(x) now clears the names of call and ... objects.
• library() will report a warning when an insufficient dependency version is masking a sufficient one later on the library search path.
• A new plot() method for class "raster" has been added.
• New check_packages_in_dir_changes() function in package tools for conveniently analyzing how changing sources impacts the check results of their reverse dependencies.
• Speed-up from Peter Haverty for ls() and methods:::.requirePackage() speeding up package loading. (PR#16133)
• New get0() function, combining exists() and get() in one call, for efficiency.
• match.call() gains an envir argument for specifying the environment from which to retrieve the ... in the call, if any; this environment was wrong (or at least undesirable) when thedefinition argument was a function.
• topenv() has been made .Internal() for speedup, based on Peter Haverty’s proposal in PR#16140.
• getOption() no longer calls options() in the main case.
• Optional use of libcurl (version 7.28.0 from Oct 2012 or later) for Internet access:
  • capabilities("libcurl") reports if this is available.
  • libcurlVersion() reports the version in use, and other details of the "libcurl" build including which URL schemes it supports.
  • curlGetHeaders() retrieves the headers for http://, https://, ftp:// and ftps:// URLs: analysis of these headers can provide insights into the ‘existence’ of a URL (it might for example be permanently redirected) and is so used in R CMD check --as-cran.
  • download.file() has a new optional method "libcurl" which will handle more URL schemes, follow redirections, and allows simultaneous downloads of multiple URLs.
  • url() has a new method "libcurl" which handles more URL schemes and follows redirections. The default method is controlled by a new option url.method, which applies also to the opening of URLs via file() (which happens implicitly in functions such as read.table.)
  • When file() or url() is invoked with a https:// or ftps:// URL which the current method cannot handle, it switches to a suitable method if one is available.
• (Windows.) The DLLs ‘internet.dll’ and ‘internet2.dll’ have been merged. In this version it is safe to switch (repeatedly) between the internal and Windows internet functions within an Rsession.

  The Windows internet functions are still selected by flag –internet2 or setInternet2(). This can be overridden for an url() connection via its new method argument.

  download.file() has new method "wininet", selected as the default by –internet2 or setInternet2().

• parent.env<- can no longer modify the parent of a locked namespace or namespace imports environment. Contributed by Karl Millar.
• New function isLoadedNamespace() for readability and speed.
• names(env) now returns all the object names of an environment env, equivalently to ls(env, all.names = TRUE, sorted = FALSE) and also to the names of the corresponding list,names(as.list(env, all.names = TRUE)). Note that although names() returns a character vector, the names have no particular ordering.
• The memory manager now grows the heap more aggressively. This reduces the number of garbage collections, in particular while data or code are loaded, at the expense of slightly increasing the memory footprint.
• New function trimws() for removing leading/trailing whitespace.
• cbind() and rbind() now consider S4 inheritance during S3 dispatch and also obey deparse.level.
• cbind() and rbind() will delegate recursively to methods::cbind2 (methods::rbind2) when at least one argument is an S4 object and S3 dispatch fails (due to ambiguity).
• (Windows.) download.file(quiet = FALSE) now uses text rather than Windows progress bars in non-interactive use.
• New function hsearch_db() in package utils for building and retrieving the help search database used by help.search(), along with functions for inspecting the concepts and keywords in the help search database.
• New function .getNamespaceInfo(), a no-check version of getNamespaceInfo() mostly for internal speedups.
• The help search system now takes keyword entries in Rd files which are not standard keywords (as given in ‘KEYWORDS’ in the R documentation directory) as concepts. For standard keyword entries the corresponding descriptions are additionally taken as concepts.
• New lengths() function for getting the lengths of all elements in a list.
• New function toTitleCase() in package tools, tailored to package titles.
• The matrix methods of cbind() and rbind() allow matrices as inputs which have 2^31 or more elements. (For cbind(), wish of PR#16198.)
• The default method of image() has an explicit check for a numeric or logical matrix (which was always required).
• URLencode() will not by default encode further URLs which appear to be already encoded.
• BIC(mod) and BIC(mod, mod2) now give non-NA numbers for arima() fitted models, as nobs(mod) now gives the number of “used” observations for such models. This fixes PR#16198, quite differently than proposed there.
• The print() methods for "htest", "pairwise.htest" and "power.htest" objects now have a digits argument defaulting to (a function of) getOption("digits"), and influencing all printed numbers coherently. Unavoidably, this changes the display of such test results in some cases.
• Code completion for namespaces now recognizes all loaded namespaces, rather than only the ones that are also attached.
• The code completion mechanism can now be replaced by a user-specified completer function, for (temporary) situations where the usual code completion is inappropriate.
• unzip() will now warn if it is able to detect truncation when unpacking a file of 4GB or more (related to PR#16243).
• methods() reports S4 in addition to S3 methods; output is simplified when the class argument is used. .S3methods() and methods::.S4methods() report S3 and S4 methods separately.
• Higher order functions such as the apply functions and Reduce() now force arguments to the functions they apply in order to eliminate undesirable interactions between lazy evaluation and variable capture in closures. This resolves PR#16093.

More at http://cran.rstudio.com/

Reference: http://www.r-bloggers.com/r-3-2-0-is-released-using-the-installr-package-to-upgrade-in-windows-os/

Main research topics:
- Comparative and Population Genomics of Plant Symbionts
- Parasite Genome Evolution
- Experimental Evolution of Microbial Symbionts and Parasites
- Phylogenomics of Early Branching Fungi

More at http://corradilab.weebly.com/

Bioinformatics Textbook Track

Find more about Rosalind puzzle at http://rosalind.info/problems/list-view/?location=bioinformatics-textbook-track

I will provide solution of all the Rosalind problem with Perl for community.

Check out the right sidebar for more links ...

http://www.stratosgenomics.com/stratos-genomics-technology

The next-generation sequencing included whole genome sequencing(WGS), transcriptome sequencing (whole cDNA sequencing, RNA-seq), digital gene expression sequencing (Tag-Seq), ChIP-Seq, and so on. And there are many sequencing platform to generate sequece, as well know Sanger/ABi(the frist generation), Solexa/illumina, SOLiD/ABi, 454/Roche. But thier sequence format is different, also they have different error type. High quality data is very important for further analysis or data mining. There are many pipeline for raw sequence quality analysis and control with few of process for reporting reads quality statistical details, trimming, filtering, and error correction. Please bookmarks them for the benefits of bioinformatics community.

https://code.google.com/p/biowiki/

https://code.google.com/p/ngs-pipeline/source/browse/#svn%2Ftrunk

NGSand Perl scripts https://code.google.com/hosting/search?q=NGS+perl&projectsearch=Search+projects

NGS and Python scripts https://code.google.com/hosting/search?q=NGS+Python&projectsearch=Search+projects

Address of the bookmark: https://code.google.com/hosting/search?q=bioinformatics&sa=Search

While your PhD or PostDoc application, it is more common that you got rejected by many professors. Don't disappoint reply it calmly.

In grad school, I shared a house with three Bioinformatics PhD students. One, when he applied to a particular professor, received a letter that said, essentially, "If you are applying because you want to enrich yourself, great. If you are applying because you want a job, you should know that you won't get one." I am trying to tell you this is because if you, with a good background in Bioinformatics, are passing up opportunities, you must be a strong candidate in many areas. Enrich yourself.

So, my suggestion is take a deep breath, forgot about all. Don’t take it personally. It's been usual processes while hunting for a good lab and professor. Take is positive, I am not sure why they reject, but don't worry perhaps the lab don't deserve you. Always remember there are billions of reasons not to hire someone for projects, especially in a research sector.

My suggestion, please do not whine about how you were a great research candidate for the post, and you just can't understand why they were so stupid as to have rejected you! This feeling will not win you any points in research, community. Especially, when in todays socially connected era everyone is linked. Remember, a nice E-mail saying, "I really wished to working with you on this project and I hope we cross paths again," is all you need to send to the professor. Send a thank you note to the professor. Thank them for the time they spend to judge you. In the future, If you and the professor (of your dream) are attending a bioinformatics conference, invite him/her to lunch (please remember to pay the bill). In today evolving scientific ere, always remember to build your solid network in order to get a job of interest. Join all possible networking sites like LinkedIn, ResearchGate, Acamedia, FB for the same reason. You as a researcher always build a bridge with student/researcher/colleague/professor who have the research potential to lead in research and hire you. Just because you didn't get this project, doesn't mean there isn't another that will open up in couple of month.

Mostly, jobs that are hard to get are hard to get. Only you can decide if the continued sacrifices are worth the expected payout. If it is, keep on plowing. Build relationships. Attend conferences.

Image ref @ JaSonYa

Bioinformatics supports to researchers
Customized training in Bioinformatics for researchers and faculty members
Support in Installing, implementing and maintaining software on computer.
Create awareness for taking preventive measure against data security
Organize workshops on thrust ares of Bioinformatics
Research Training to students of Biotechnology and Bioinformatics

More at http://bioinfo.bisr.res.in/index.php