Open ghost opened 11 years ago
C is the updated EBNF (i've just pushed it to git), whereas B is the actual definition file
I've also pushed Reports/siggendef.def to git if it's helpful.
Also this report is boring to write :(
On 5 June 2013 15:01, GeorgeAyris notifications@github.com wrote:
We need additional definition files that incorporate the siggen, has anyone done anything so far along these lines?
Also, how does appendix C vary from appendix B?
? Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23 .
I think i'm going to struggle to get anywhere near 10 pages, since I'm "done" and it's only 4 pages not counting title page/appendices
Yep, though at least it involves a minimum of thinking. Thanks for all that! Let me know if there's anything else I need to do.
On 5 June 2013 15:05, James Glanville notifications@github.com wrote:
C is the updated EBNF (i've just pushed it to git), whereas B is the actual definition file
I've also pushed Reports/siggendef.def to git if it's helpful.
Also this report is boring to write :(
On 5 June 2013 15:01, GeorgeAyris notifications@github.com wrote:
We need additional definition files that incorporate the siggen, has anyone done anything so far along these lines?
Also, how does appendix C vary from appendix B?
? Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23> .
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18977572 .
And it is "up to 10 pages", so surely 4 is (officially) ok?
well yeah, but I feel like I should get at least 6-7 pages done :(
On 5 June 2013 15:25, adh635 notifications@github.com wrote:
And it is "up to 10 pages", so surely 4 is (officially) ok?
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18978908 .
Also, what is meant to go into appendix C? the updated EBNF?
On 5 June 2013 15:28, James Glanville notifications@github.com wrote:
well yeah, but I feel like I should get at least 6-7 pages done :(
On 5 June 2013 15:25, adh635 notifications@github.com wrote:
And it is "up to 10 pages", so surely 4 is (officially) ok?
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18978908> .
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979328 .
yes i think so.
On 5 June 2013 15:32, GeorgeAyris notifications@github.com wrote:
Also, what is meant to go into appendix C? the updated EBNF?
On 5 June 2013 15:28, James Glanville notifications@github.com wrote:
well yeah, but I feel like I should get at least 6-7 pages done :(
On 5 June 2013 15:25, adh635 notifications@github.com wrote:
And it is "up to 10 pages", so surely 4 is (officially) ok?
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18978908> .
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979328> .
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979941 .
Ta, is the software in a final functioning form?
On 5 June 2013 15:44, James Glanville notifications@github.com wrote:
yes i think so.
On 5 June 2013 15:32, GeorgeAyris notifications@github.com wrote:
Also, what is meant to go into appendix C? the updated EBNF?
On 5 June 2013 15:28, James Glanville notifications@github.com wrote:
well yeah, but I feel like I should get at least 6-7 pages done :(
On 5 June 2013 15:25, adh635 notifications@github.com wrote:
And it is "up to 10 pages", so surely 4 is (officially) ok?
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18978908>
.
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979328> .
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979941> .
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18981073 .
We still have the same bug with render in the on paint function being called with no arguments meaning the trace is being reset.
On 5 June 2013 17:26, George Ayris georgeayris@gmail.com wrote:
Ta, is the software in a final functioning form?
On 5 June 2013 15:44, James Glanville notifications@github.com wrote:
yes i think so.
On 5 June 2013 15:32, GeorgeAyris notifications@github.com wrote:
Also, what is meant to go into appendix C? the updated EBNF?
On 5 June 2013 15:28, James Glanville notifications@github.com wrote:
well yeah, but I feel like I should get at least 6-7 pages done :(
On 5 June 2013 15:25, adh635 notifications@github.com wrote:
And it is "up to 10 pages", so surely 4 is (officially) ok?
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18978908>
.
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979328> .
— Reply to this email directly or view it on GitHub< https://github.com/JamesGlanville/GF2/issues/23#issuecomment-18979941> .
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18981073 .
Also the monitor lists require resetting on a new file
Also, how was the new dtype tested?
I tested it with the shift register definition file - it works as expected so the next dtype doesn't always get valid data if the previous one updates.
On 5 June 2013 18:49, GeorgeAyris notifications@github.com wrote:
Also, how was the new dtype tested?
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-18994751 .
Do we have a method of showing the test results obtained for the example definition files? They're required in appendix B but currently the software isn't drawing any traces...
No traces what so ever?
On 6 June 2013 00:50, adh635 notifications@github.com wrote:
Do we have a method of showing the test results obtained for the example definition files? They're required in appendix B but currently the software isn't drawing any traces...
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19016810 .
Well, they just drop back to 0 for every cycle...
Also, where do I get the latest EBNF and testfiles (and which test files should I be sticking in the report?)
0 as in low?
On 6 June 2013 00:54, adh635 notifications@github.com wrote:
Well, they just drop back to 0 for every cycle...
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19016976 .
yup
Have you tried commenting out render in onPaint?
On 6 June 2013 00:59, adh635 notifications@github.com wrote:
yup
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19017156 .
Ok, that works. Can you push that to github so the code we submit has it?
Now what test files do I need to run?
Done, though it introduces the problem of resizing not re-drawing the trace.
I think you want the two from the original report plus siggen.def, which is in the reports folder.
James is it possible to get a quick circuit diagram for that definition file?
Out of interest have either of you produced any of the team appendices that you can share?
not yet, I would suggest we each take one but I guess a lot of it is reusable from the interim reports?
Fair, I'm struggling to work out what exactly I'm testing with the d-type functionality so a screen shot showing a test result of that would be good for me. The specification of the definition file I think Glanville has already sorted and uploaded into the spec folder. The brief description shouldn't take long and could be quickly done when the files are moved into the team directory?
On 6 June 2013 01:49, adh635 notifications@github.com wrote:
not yet, I would suggest we each take one but I guess a lot of it is reusable from the interim reports?
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19018836 .
I've added some screenshots for the test files. (They're in Reports/Andy_Final_Report
Notes:
Has anyone copied their files into the team directory?
On 6 June 2013 13:05, adh635 notifications@github.com wrote:
I've added some screenshots for the test files. (They're in Reports/Andy_Final_Report
Notes:
- testgates worked pretty much as expected.
- shift_register did not. Doesn't seem to be working at all.
- I cheated on sig gen - I renamed the monitor on s as invsig so it looks like the inverted signal is what it should be...
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19040654 .
I haven't. Could you?
I can, but I'm not confident on how to do it remotely.
On 6 June 2013 13:52, adh635 notifications@github.com wrote:
I haven't. Could you?
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19042872 .
If you're not sure I'm happy to do it, would be useful if you could check though.
Could you both confirm if you're happy for me to do it NOW or if you want me to wait for you to change anything?
I'm happy for now because I'm not going to have time to change anything.
On 6 June 2013 13:59, adh635 notifications@github.com wrote:
If you're not sure I'm happy to do it, would be useful if you could check though.
Could you both confirm if you're happy for me to do it NOW or if you want me to wait for you to change anything?
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19043225 .
I'm going to put the code in the directory now. Has anyone done a description of the files in the team directory?
for what it's worth i've shared mine, but it was lousy and lazy and rubbish. i haven't managed to get it fixed properly so fine to copy files by me.
On 6 June 2013 14:23, adh635 notifications@github.com wrote:
I'm going to put the code in the directory now. Has anyone done a description of the files in the team directory?
— Reply to this email directly or view it on GitHubhttps://github.com/JamesGlanville/GF2/issues/23#issuecomment-19044550 .
It was useful in reminding me to copy the test directory though!
Could someone try running the code in the shared directory to make sure I've copied everything required and given the right permissions?
Have finished my report and pushed it.
Feel free to copy anything useful!
We need additional definition files that incorporate the siggen, has anyone done anything so far along these lines?
Also, how does appendix C vary from appendix B?