|
It's newline-delimited. I'm just wondering if there's a term for it, like CSV for comma-separated.
What is your notion of series data?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Isn't CSV technically newline-delimited as well as comma separated?
I guess series data, I was thinking if it's ordered like time series, but none of the values are datetime. Not sure if that makes sense.
Order Number Value
10 11.2
11 16.5
12 18.5
|
|
|
|
|
wizardzz wrote: Isn't CSV technically newline-delimited as well as comma separated?
Sure. Then "my" format would be "empty-line-delimited and newline-separated" 
wizardzz wrote: I was thinking if it's ordered like time series, but none of the values are datetime.
No, that's not the right term for it then. I think I'll go with "something key-value something" 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I would call it "sectioned data" where each record is a "section" of the file starting with a header and having its values in the remainder of the section.
I've had to parse data like this a few times before, some not nearly as straightforward as yours though.
|
|
|
|
|
Is there any real value in verifying each copy? I've never seen an error reported, and it takes 25 minutes to verify a 6 minute copy. How often do copies really go bad?
Will Rogers never met me.
|
|
|
|
|
I had some errors with older device and fast (too fast) copy, with modern devices the quality is mostly depends on the media and not on the device...
Few advises:
1. Use high quality media if the content is important.
2. Wait a bit more for the copy and use copy speed supported both by the media and the device...
3. Give the copy software enough resources to run - waiting can go wrong.
4. If it can be avoided do not use media like hard disk - write it once...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It was a common problem in the old times when buffer under runs were a common reason for creating coasters.
Nowadays most (probably all) writers have buffer underrun protection, where the writer is able to shut the laser and restart writing where it failed.
|
|
|
|
|
While buffer underruns is a problem of the past, it's still possible to burn a DVD, not get any error, but then still fail to read it back.
Personally, whenever I need to make sure a DVD I just created has no error, I put the disc in a separate drive, in another machine, and read it back from there (Select All, drag to a folder on the hard drive). If nothing else, that allows me to continue burning another DVD while the other one is busy reading the first one back. And that tends to be quicker than most burning software's Verify step. Once that's done, I'm confident the disc can be read back with a drive independently of the one that created it.
[Edit] I always buy 8x DVDs but never burn at more than 4x.
|
|
|
|
|
I must have burnt over a thousand DVDs and CDs over the past 15 years. I have had no issues that I can remember, except in the beginning, when I had regular buffer under-runs. I try to stick to Verbatim. It has never disappointed me.
Get me coffee and no one gets hurt!
|
|
|
|
|
Rather depends on what you're using them for, doesn't it? If it's a one-off copy of changeable data in its present state to be sent up with the next trip to the ISS then yes. If it's something where you can just burn another copy and get it to whoever couldn't get the original to work in less than two shakes a of a lamb's tail then no.
I am not a number. I am a ... no, wait!
|
|
|
|
|
Hi, I am a student working my way for an associate’s degree in Information technology. My main focus is computer programming and I have finals coming up, but for one class I have to do a report about what it’s like to be computer programmer. This is a little hard for me since I have no connections to anyone that is currently employed in the field.
I have come up with some questions if anyone on here would be willing to answer my questions and send them to me via email it would be greatly appreciated and I would really enjoy getting a better understanding of what the life of a programmer is really like.
There is roughly 30 questions, but feel free to answer as many as you like. When I get around to reading it and I liked what I seen then I will use it for my final project, which is an informational interview report. I will also email you back informing you that I am using you as my interviewee for the project.
My email address is xxxxxxxxxxxx@hotmail.com and I will attach a link to a Google Docs file to this post for anyone who is interested. Thanks to anyone who is willing to take the time to help me with this, it’s greatly appreciated.
modified 27-Feb-16 21:19pm.
|
|
|
|
|
Kore1322 wrote: what it’s like to be computer programmer
It's wall-to-wall chicks: Sex & Drugs & Rock & Roll, maaaaan.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I just was on my way to warn the guy that all computer programmers are liars...I can skip that now 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You think we should tell him "it's indoor work with no heavy lifting"? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: no heavy lifting
I use a special keyboard with metal plate on its bottom - that's heavy...
Every time I want to hit the computer, not only I have to lift it, but also have to crawl under my desk to actually hit it...I would not say that, this is an easy work...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Steel toe-cap boots. Just kick the damn thing!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Boots! 10 out of 12 months I wear sandal!!! And take them off too...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Please, please tell me that's not "with socks"? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No socks...Too hot for me...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Yup, the chicks are all driven by hormonal impulses which compel them to offer their hot bodies to men with a high earning potential, and few earn so much as programmers. Most programmers die of sexual exhaustion, usually in their early fifties.
Will Rogers never met me.
|
|
|
|
|
Just an aside are these 'chicks' you speak of kinda like the ones from Dilbert that reside on the moon?
|
|
|
|
|
If he doesn't believe you, he can take a look at your photo. Hard to believe you're only 26.
This space for rent
|
|
|
|
|
The white is because of the intensive life style...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Quote: When 900 years old you reach, look as good, you will not.
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Roger Wright wrote: Most programmers die of sexual exhaustion, usually in their early fifties.
I guess I'll be living a bit longer then. 
Marc
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
