"unregonized arguments: Go" using the columns of a tab-delimited txt to automate a terminal command w/ multiple arguments

By -

I'm trying to simplify running a large number of varying operations on some sets of data, where there are 3 variables that might vary each time I run the command: 1) an output name, 2) a list of treatment samples and 3) a list of controls to match those treatments to. Sometimes the treatments for one comparison are the controls for another, so there is no way to solve this with a clever naming scheme that simplifies each comparison to a single variable.

Output Name Column Treatment Names Column Control Sample Column
name1 sample1,sample2 control1
... ... ...

What I've been trying:

while IFS=$'\t' read -r Output_Name Treatment Control
do
    command -argument1 $Treatment -argument2 $Control -argument3 $Output_Name
done < ../Testing_Table.txt

But I get an error: "unrecognized argument: Go"

When I simplify this to just echo back all of the variables, I can see that there is a "Go" after the $Treatment variable that I cannot account for.

For instance

while IFS=$'\t' read -r Output_Name Treatment Control
do
    echo "Treatment:" $Treatment \n "Control:" $Control \n "Name:=" $Output_Name
done < ../Testing_Table.txt

Might output something automate a command w/ multiple argumentlike this for the first row of the testing table file. I can't account for where "Go" is coming from as it's not anywhere directly within my code or in my tab-delimited file.

Treatment: sample1,sample2 Go
Control: control1
Name: name1


from Recent Questions - Stack Overflow https://ift.tt/37Qg3KQ
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more