Genome Workbench can display sequence data in many ways, including graphical sequence views, various alignment views, phylogenetic tree views, and tabular views of data. It can also align your private data to data in public databases, display your data in the context of public data, and retrieve BLAST results.

Genome Workbench is built on the NCBI C++ ToolKit and uses cross-platform APIs for graphics. It runs on your local machine, and is available for Windows 2000/XP, Linux, MacOS X, and various flavors of Unix.

NCBI Genome Workbench is an integrated application for viewing and analyzing sequence data. Genome Workbench was developed entirely in-house at NCBI and makes use of the NCBI C++ ToolKit. The C++ ToolKit provides a convenient and flexible cross-platform API for managing system internals, database connections, network sockets, and the NCBI data model. In addition, the C++ ToolKit provides the Object Manager, which abstracts handling of sequences and sequence-related objects.

 New Features in Genome Workbench 2.7.15

• Multiple Alignment View: implemented adaptive feature display when zooming in
• Active Objects Inspector replaces Selection Inspector. New View should offer an improved selection context examination. See Using Active Objects Inspector tutorial for more details.
• Binary packages for Linux OpenSUSE 13.1 are now available

Bug Fixes and Improvements in Genome Workbench 2.7.15

• Fixed major issue with OpenGL overlay/scrolling. Could cause crashes or view scrolling irregularities
• Multiple Pane View: fixed crash on loading BLAST results
• Graphical Sequence View: fixed crash on zooming in and out, related to SNP track
• Graphical Sequence View: fixed Go To Position dialog to give better diagnostics in case of a user error
• Graphical Sequence View: PDF export fixed rendering of Markers with commas in the name
• Text View / Flat File: fixed Mac OS rendering issues
• Text View / Flat File: performance optimization, extended capabilities of real-time rendering of molecules to tens of thousands
• File Import: optimization improvement to speed up load of files containing multiple project items
• File Import: remapping stage now shows accession.version and description of molecules, instead of plain GI numbers
• Mac OS: improved tooltips for toolbar buttons
• Phylogenetic Tree Builder Tool: improved diagnostics of errors
• Multiple Alignment View: optimizations to avoid main GUI freezes
• Open Dialog: removed duplicate elements in table of genomes (load Genome)
• PDF export: fixed issue with XREF table errors
• Tree View: fixed issues with showing Force Layout progress on Mac OS
• Tree View: PDF export fixed issues for showing labels of collapsed nodes
• Tree View: added an option to stop layout
• Tree View: broadcasting mechanism fixed not to accumulate selected nodes

Reference:

NCBI news

http://www.ncbi.nlm.nih.gov/tools/gbench/

The following 5 questions are those that I have heard many times during the job-search process. There is no reason for not planning responses in such situations.

1. Tell Us About Yourself
This is a very typical opener in interviews. It's a perfect question to ask, and getting something planned will really help you concentrate and ease in the conversation. However, you need to make sure that your response is applicable to the job you're interviewing.
It's probably better to keep your answer professional. Try to include these in the answer as well: where did your love of science and bioinformatics come from? How the heck did you end up in this field? Why programming and scripting ?

2. What is your plan for your bioinformatics career? / How do you look at yourself in five years? / How are your personal objectives to accomplish these goals / What are the plan for your research fundings ?

Your CV/resume has already impressed the selection panel if you have been invited for an interview. The questions from the bioinformatics interview team provide an incentive for you to market yourself and illustrate the work in question with the most appropriate knowledge.

3. What do you understand about the job description/What would your suggested research path be if you were a successful candidate?
Summarize the specifics of the advertised bioinformatics position in your own words. Follow on with some suggestions of how you want to extend your research and create your own projects within the community.

4. Will you work as a group or do you want to work on your own?
This requirement can vary from jobs to job, so when addressing, be alert. A company/research PI may need a bioinformatician that is able to work on a single project autonomously, or they may need a person who can help direct and organize a team. In your response, refer to the job description.

5. What particular methods have you used to date with your experiments?
You might have experience with all the laboratory techniques described in the job description, but stress the ones you highly experienced with. Highlight your professional abilities and stress that you are extremely capable of mastering new techniques with others ...

At the end of the day, remember that you're questioning the jury as well as they're interviewing you. You will ought to think of any questions you would like the interview panel to pose. This indicates that you have done your homework and serious about the position.

All the best for your future job interview.

The Vicoso group is interested in understanding several aspects of the biology of sex chromosomes, and the evolutionary processes that shape their peculiar features. By combining the use of next-generation sequencing technologies with studies in several model and non-model organisms, they can address a variety of standing questions, such as: Why do some Y chromosomes degenerate while others remain homomorphic, and how does this relate to the extent of sexual dimorphism of the species? What forces drive some species to acquire global dosage compensation of the X, while others only compensate specific genes? What are the frequency and molecular dynamics of sex-chromosome turnover?

More at https://ist.ac.at/en/research/vicoso-group/
http://pub.ist.ac.at/~bvicoso/

More at https://www.nature.com/articles/s41467-021-22671-6

Address of the bookmark: https://github.com/dmcblab/InfoGenomeR

Shell history search command

Type history at a shell prompt:
$ history

It will display the list of all used commandline history with an serial number.

To search particular command, enter:
$ history | grep command-name
$ history | egrep -i 'scp|ssh|ftp'
Emacs Line-Edit Mode Command History Searching

To get previous command containing string, hit [CTRL]+[r] followed by search string:

(reverse-i-search):

To get previous command, hit [CTRL]+[p]. You can also use up arrow key.

CTRL-p

To get next command, hit [CTRL]+[n]. You can also use down arrow key.

CTRL-n

fc command

Apart from hostory command there are fc command to extract the command from history. The fc stands for either "find command" or "fix command.

For example list last 10 command, enter:
$ fc -l 10
To list commands 130 through 150, enter:
$ fc -l 130 150
To list all commands since the last command beginning with ssh, enter:
$ fc -l ssh
You can edit commands 1 through 5 using vi text editor, enter:
$ fc -e vi 1 5

Delete command history

The -c option causes the history list to be cleared by deleting all of the entries:
$ history -c

Address of the bookmark: https://github.com/Magdoll/Cogent

Details are available at www.nehu.ac.in and www.bicnehu.ac.in.

Applications must reach the undersigned within 15 days from the date of publication of this advertisement.

Prof. Pramod Tandon. PI/Mr. Devendra Kumar Biswal (Co-PI)

Availability and implementation: The software runs under Linux, has the GPLv3 licence and is freely available from http://sanger-pathogens.github.io/iva

https://pubmed.ncbi.nlm.nih.gov/25725497/

Address of the bookmark: https://github.com/sanger-pathogens/iva