Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1165 closed enhancement (worksforme)

Option to insert Block number when importing reporter map with Meta grid X/Y

Reported by: Johan Vallon-Christersson Owned by: everyone
Priority: minor Milestone:
Component: coreplugins Version:
Keywords: Cc:

Description

When using plugin: Reporter map importer. I have a reporter map with Meta grid X/Y and Column/Row? but without Block numbers.

After importing I get message 'Done: 32016 feature(s) inserted; 48 block(s) inserted'. Everything looks good and correctly imported. However, Block numbers for all coordinates are set to 0.

It would be useful to have the option to configure the Reporter map importer to insert block numbers for the inserted blocks.

The alternative is for the user to create the block numbers in the reporter map before importing. This works as well. Having the option to let the plugin do the work is simply an enhancement that can save some time.

Change History (3)

comment:1 Changed 13 years ago by Nicklas Nordborg

Resolution: worksforme
Status: newclosed

This can be done in the configuration settings. Just enter the desired block value in the 'Block' field.

comment:2 in reply to:  1 Changed 13 years ago by Jari Häkkinen

Replying to nicklas:

This can be done in the configuration settings. Just enter the desired block value in the 'Block' field.

Wouldn\t this just create another constant rather than '0'? I think the idea is that when no block information is available in the imported file, the block should be assigned a number automatically reflecting the detected blocks (the blocks are currently detected by the plug-in). This would give each block a unique number. Currently a '0' is set for all blocks, but it would be nice if the actually block count was used to set each block number. This block number is inferred from meta_x and meta_y information without user interaction.

The block number could be set by row-major numbering using the meta coordinates

meta_x meta_y block
1      1      1
1      2      2
2      1      3
2      2      4

comment:3 Changed 13 years ago by Nicklas Nordborg

I came to think about that it is not a good idea to set the block number if you intend to use the meta-coordinates when importing raw data that doesn't have block number. Spot identification with coordinates can be done in two ways:

  1. block, row, column: This is used when block != 0
  2. meta-x, meta-y, row, column: This is used when block == 0

So, if the block is set in the array design, the meta-coordinates are not used when matching spots from the raw data file. Also note that within a single block, all [row, column] values must be different.

Note: See TracTickets for help on using tickets.