Input file error-"Bad format in data source"

1,830 views
Skip to first unread message

Santosh

unread,
Dec 6, 2013, 8:56:59 PM12/6/13
to structure...@googlegroups.com
Guys,
I am new to structure. I am using version 2.3.4. I am facing problem to upload the file. This may be simple step for you but it is creating pain for me.
My parameters are like this:

no of indviduals:9
ploidy:2
number of loci:14
missing data value:-9

I am getting the message"Bad format in data source" Expect 15 entrees at line 2" i dont what is the problem?

I tried by adding recessive allele row, removing marker names all the factors. Please educate me on this.Thanks

Vikram Chhatre

unread,
Dec 7, 2013, 9:48:16 AM12/7/13
to structure-software
This type of error is usually caused by:

1. Mismatch between number of columns in data file and expectations based on the parameters specified, e.g. POPDATA, LOCDATA columns etc.

2. Wrong or missing EOL (end of line) character.  

I suggest familiarizing yourself with the software using the example datasets first and then closely following the instructions in user manual for formatting the data file.  User a proper text editor (Notepad++ on Windows) and not Word/Excel to prepare the datafile.

All the best
V




--
You received this message because you are subscribed to the Google Groups "structure-software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to structure-softw...@googlegroups.com.
To post to this group, send email to structure...@googlegroups.com.
Visit this group at http://groups.google.com/group/structure-software.
For more options, visit https://groups.google.com/groups/opt_out.

Santosh

unread,
Jan 10, 2014, 4:03:01 PM1/10/14
to structure...@googlegroups.com
Thanks Vikram.


On Saturday, December 7, 2013 7:48:16 AM UTC-7, Vikram Chhatre wrote:
This type of error is usually caused by:

1. Mismatch between number of columns in data file and expectations based on the parameters specified, e.g. POPDATA, LOCDATA columns etc.

2. Wrong or missing EOL (end of line) character.  

I suggest familiarizing yourself with the software using the example datasets first and then closely following the instructions in user manual for formatting the data file.  User a proper text editor (Notepad++ on Windows) and not Word/Excel to prepare the datafile.

All the best
V

On Fri, Dec 6, 2013 at 7:56 PM, Santosh <rajp...@gmail.com> wrote:
Guys,
I am new to structure. I am using version 2.3.4. I am facing problem to upload the file. This may be simple step for you but it is creating pain for me.
My parameters are like this:

no of indviduals:9
ploidy:2
number of loci:14
missing data value:-9

I am getting the message"Bad format in data source" Expect 15 entrees at line 2" i dont what is the problem?

I tried by adding recessive allele row, removing marker names all the factors. Please educate me on this.Thanks

--
You received this message because you are subscribed to the Google Groups "structure-software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to structure-software+unsub...@googlegroups.com.

Chris Yesmont

unread,
Apr 4, 2014, 5:23:23 AM4/4/14
to structure...@googlegroups.com

I see this is an old question, but I came across it when having a similar problem and would like to post my solution.

I was getting the same type of "Bad format in data source..."
My problem turned out was 2. Missing EOL character suggested by Vikram.

The problem arises from the carriage return differences in unix and windows when creating the tab delimited format. Essentially there are extra tabs created when converting from excel on mac to tab delimited.

The solution was simply to save as "Window's formatting text" .txt instead of tab delimited.

Reply all
Reply to author
Forward
0 new messages