Talk:Data reader - Revision history

Jpye: /* Data Reader Talk Page */

2010-06-01T13:55:25Z

Data Reader Talk Page

← Older revision		Revision as of 13:55, 1 June 2010
Line 3:		Line 3:
	Please capture here thoughts and ideas that might not be appropriate in the main page. Experimental features, corrections, toDO's, wishes, etc. The idea is to keep the page itself as documentation and let the talk page be the discussion/developement forum. [[User:JoseZapata\|Jose Zapata]] 23:30, 26 July 2009 (UTC)		Please capture here thoughts and ideas that might not be appropriate in the main page. Experimental features, corrections, toDO's, wishes, etc. The idea is to keep the page itself as documentation and let the talk page be the discussion/developement forum. [[User:JoseZapata\|Jose Zapata]] 23:30, 26 July 2009 (UTC)

	:TODO (high priority, very easy): Other file formats: we should add support for the Australian BoM's new RMY (prev TMY) file format. It's the same as ACDB format, but with three extra digits added to the end. [[User:Jpye]] 07:41, 27 July 2009 (UTC)		TODO (high priority, very easy): Other file formats: we should add support for the Australian BoM's new RMY (prev TMY) file format. It's the same as ACDB format, but with three extra digits added to the end. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	::Agree, would you like this done within GSOC? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)		:Agree, would you like this done within GSOC? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	:TODO (high priority, moderate difficulty): Add support for CSV files. Bear in mind that Excel outputs files with quoting of (some/all?) values and some escape characters (eg \", not sure); a fully general implementation could be difficult. [[User:Jpye]] 07:53, 27 July 2009 (UTC)		TODO (high priority, moderate difficulty): Add support for CSV files. Bear in mind that Excel outputs files with quoting of (some/all?) values and some escape characters (eg \", not sure); a fully general implementation could be difficult. [[User:Jpye]] 07:53, 27 July 2009 (UTC)
	::I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)=		:I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)=

	:TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. [[User:Jpye]] 07:41, 27 July 2009 (UTC)		TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	::I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)		:I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	:TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. [[User:Jpye]] 07:41, 27 July 2009 (UTC)		TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	::I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)		:I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	:TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. [[User:Jpye]] 07:53, 27 July 2009 (UTC)		TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. [[User:Jpye]] 07:53, 27 July 2009 (UTC)

	:TODO check monotonic increase of independent variable [[User:JoseZapata]] 04:08, 24 August 2009 (UTC)		TODO check monotonic increase of independent variable [[User:JoseZapata]] 04:08, 24 August 2009 (UTC)

Jpye: /* Data Reader Talk Page */

2010-06-01T13:54:57Z

Data Reader Talk Page

← Older revision		Revision as of 13:54, 1 June 2010
Line 3:		Line 3:
	Please capture here thoughts and ideas that might not be appropriate in the main page. Experimental features, corrections, toDO's, wishes, etc. The idea is to keep the page itself as documentation and let the talk page be the discussion/developement forum. [[User:JoseZapata\|Jose Zapata]] 23:30, 26 July 2009 (UTC)		Please capture here thoughts and ideas that might not be appropriate in the main page. Experimental features, corrections, toDO's, wishes, etc. The idea is to keep the page itself as documentation and let the talk page be the discussion/developement forum. [[User:JoseZapata\|Jose Zapata]] 23:30, 26 July 2009 (UTC)

			:TODO (high priority, very easy): Other file formats: we should add support for the Australian BoM's new RMY (prev TMY) file format. It's the same as ACDB format, but with three extra digits added to the end. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
			::Agree, would you like this done within GSOC? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	: TODO (high priority, ~~very easy~~): ~~Other file formats: we should add~~ support for ~~the Australian BoM's new RMY~~ (~~prev TMY~~) ~~file format. It's the same as ACDB format~~, ~~but with three extra digits added to the end~~. [[User:Jpye]] 07:41, 27 July 2009 (UTC)		:TODO (high priority, moderate difficulty): Add support for CSV files. Bear in mind that Excel outputs files with quoting of (some/all?) values and some escape characters (eg \", not sure); a fully general implementation could be difficult. [[User:Jpye]] 07:53, 27 July 2009 (UTC)
	~~<dl><dd> Agree~~, ~~would you like this done within GSOC?~~ [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)		::I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)=
	~~</dd></dl>~~

	: ~~Agree~~, would ~~you~~ like ~~this done within GSOC?~~ [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)		:TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
			::I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	: TODO (~~high~~ priority, ~~moderate difficulty~~): ~~Add support~~ for ~~CSV files~~. ~~Bear in mind~~ that ~~Excel outputs files with quoting of (some/all?) values and some escape characters (eg \"~~, not ~~sure); a fully general implementation could be difficult~~. [[User:Jpye]] 07:53, 27 July 2009 (UTC)		:TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
			::I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	~~<dl><dd> I dont think is worth the effort~~ to ~~code for~~ a ~~"MS proof" csv file AFAICT most software produce good quality~~ CSV ~~files (including Excel~~)~~. If the~~ data file ~~is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it~~. [[User:~~JoseZapata~~]] 05:55, ~~12 August~~ 2009 (UTC)		:TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. [[User:Jpye]] 07:53, 27 July 2009 (UTC)
	~~</dd></dl>~~

	: I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)		:TODO check monotonic increase of independent variable [[User:JoseZapata]] 04:08, 24 August 2009 (UTC)


	: TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	<dl><dd> I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	~~</dd></dl>~~

	: I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)



	: TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	<dl><dd> I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)
	~~</dd></dl>~~

	: I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)


	~~: TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. [[User:Jpye]] 07:53, 27 July 2009 (UTC)~~

	: TODO check monotonic increase of independent variable [[User:JoseZapata]] 04:08, 24 August 2009 (UTC)

Jpye at 13:53, 1 June 2010

2010-06-01T13:53:15Z

UploadBot: Restored page from Google Cache, uploaded by John Pye

2010-05-13T13:58:24Z

Restored page from Google Cache, uploaded by John Pye

New page

==Data Reader Talk Page==

Please capture here thoughts and ideas that might not be appropriate in the main page. Experimental features, corrections, toDO's, wishes, etc. The idea is to keep the page itself as documentation and let the talk page be the discussion/developement forum. [[User:JoseZapata|Jose Zapata]] 23:30, 26 July 2009 (UTC)

: TODO (high priority, very easy): Other file formats: we should add support for the Australian BoM's new RMY (prev TMY) file format. It's the same as ACDB format, but with three extra digits added to the end. <a href="/User:Jpye" title="User:Jpye">Jpye</a> 07:41, 27 July 2009 (UTC)
<dl><dd> Agree, would you like this done within GSOC? <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)
</dd></dl>

: Agree, would you like this done within GSOC? <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)

: TODO (high priority, moderate difficulty): Add support for CSV files. Bear in mind that Excel outputs files with quoting of (some/all?) values and some escape characters (eg \", not sure); a fully general implementation could be difficult. <a href="/User:Jpye" title="User:Jpye">Jpye</a> 07:53, 27 July 2009 (UTC)

<dl><dd> I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)
</dd></dl>

: I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)

: TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. <a href="/User:Jpye" title="User:Jpye">Jpye</a> 07:41, 27 July 2009 (UTC)
<dl><dd> I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions<a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)

</dd></dl>

: I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions<a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)

: TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. <a href="/User:Jpye" title="User:Jpye">Jpye</a> 07:41, 27 July 2009 (UTC)
<dl><dd> I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)
</dd></dl>

: I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 05:55, 12 August 2009 (UTC)

: TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. <a href="/User:Jpye" title="User:Jpye">Jpye</a> 07:53, 27 July 2009 (UTC)

: TODO check monotonic increase of independent variable <a href="/User:JoseZapata" title="User:JoseZapata">Jose Zapata</a> 04:08, 24 August 2009 (UTC)

← Older revision		Revision as of 13:53, 1 June 2010
Line 4:		Line 4:


	: TODO (high priority, very easy): Other file formats: we should add support for the Australian BoM's new RMY (prev TMY) file format. It's the same as ACDB format, but with three extra digits added to the end. ~~<a href="/User:Jpye" title="~~User:Jpye~~">Jpye</a>~~ 07:41, 27 July 2009 (UTC)		: TODO (high priority, very easy): Other file formats: we should add support for the Australian BoM's new RMY (prev TMY) file format. It's the same as ACDB format, but with three extra digits added to the end. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	<dl><dd> Agree, would you like this done within GSOC? ~~<a href="/User:JoseZapata" title="~~User:JoseZapata~~">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		<dl><dd> Agree, would you like this done within GSOC? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)
	</dd></dl>		</dd></dl>

	: Agree, would you like this done within GSOC? ~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		: Agree, would you like this done within GSOC? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	: TODO (high priority, moderate difficulty): Add support for CSV files. Bear in mind that Excel outputs files with quoting of (some/all?) values and some escape characters (eg \", not sure); a fully general implementation could be difficult. ~~<a href="/~~User:Jpye~~" title="User:Jpye">Jpye</a>~~ 07:53, 27 July 2009 (UTC)		: TODO (high priority, moderate difficulty): Add support for CSV files. Bear in mind that Excel outputs files with quoting of (some/all?) values and some escape characters (eg \", not sure); a fully general implementation could be difficult. [[User:Jpye]] 07:53, 27 July 2009 (UTC)

	<dl><dd> I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. ~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		<dl><dd> I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)
	</dd></dl>		</dd></dl>

	: I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. ~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		: I dont think is worth the effort to code for a "MS proof" csv file AFAICT most software produce good quality CSV files (including Excel). If the data file is not properly formated, (as in values sepparated by commas and nothing else) the data reader should reject it. [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)


	: TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. ~~<a href="/User:Jpye" title="~~User:Jpye~~">Jpye</a>~~ 07:41, 27 July 2009 (UTC)		: TODO (medium priority, moderately difficult): Support for lookup tables with two independent variables. For example, we could use it to code up Jeff's results on the efficiency of a dish field for different sun angles. Examples of independent variables would be altitude and azimuth angles. I believe that TRNSYS implements this kind of thing. This would require a generalised spline implementation. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	<dl><dd> I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		<dl><dd> I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)

	</dd></dl>		</dd></dl>

	: I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		: I thought a single independent variable was part of the scope definition for the data reader. I suppose it makes sense, specially for situations like dish efficiency fields where tabulation of data is faster than coding the efficiency algorithm like other extfunctions[[User:JoseZapata]] 05:55, 12 August 2009 (UTC)



	: TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. ~~<a href="/User:Jpye" title="~~User:Jpye~~">Jpye</a>~~ 07:41, 27 July 2009 (UTC)		: TODO (low priority, fiendishly difficult): Support for integer/boolean input data. There will be cases when input data could contain on-off stuff that we would like to feed into a simulation. Currently very difficult to implement, because the '''external''' relation interface only provides for rels, not logrels. [[User:Jpye]] 07:41, 27 July 2009 (UTC)
	<dl><dd> I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? ~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		<dl><dd> I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)
	</dd></dl>		</dd></dl>

	: I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? ~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 05:55, 12 August 2009 (UTC)		: I dont see how boolean data should be imported different from real data. The trick is in the interpolation. If a signal changes from 0 to 1 , what is the value in between? [[User:JoseZapata]] 05:55, 12 August 2009 (UTC)


	: TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. ~~<a href="/~~User:Jpye~~" title="User:Jpye">Jpye</a>~~ 07:53, 27 July 2009 (UTC)		: TODO (medium priority, very easy): Add a link to a complete working example, preferable including a sample (CSV?) data file. [[User:Jpye]] 07:53, 27 July 2009 (UTC)

	: TODO check monotonic increase of independent variable ~~<a href="/~~User:JoseZapata~~" title="User:JoseZapata">Jose Zapata</a>~~ 04:08, 24 August 2009 (UTC)		: TODO check monotonic increase of independent variable [[User:JoseZapata]] 04:08, 24 August 2009 (UTC)