last day (14 days later) » 

1:31 PM
@Jacccy OK, this is odd and most likely a problem of the relative path.
 
Found it =)
..the room

Yes I guess it is a problem of the path
 
What happens if you do
FileExistsQ /@ files
 
{False,False,False,False,False,False,False,False,False,False}
 
What happens if you do
 
Can it be a problem of the file name?

20180627_532nm_100x_50um_2s_60Acc_15mW_mitMetbehandelt_0s_wafer16_117_Spec.Data 1.txt
 
1:35 PM
FileExistsQ[AbsoluteFileName[#]]& /@ files
 
{FileExistsQ[$Failed],FileExistsQ[$Failed],FileExistsQ[$Failed],FileExistsQ[$Fai‌​led],FileExistsQ[$Failed],FileExistsQ[$Failed],FileExistsQ[$Failed],FileExistsQ[$‌​Failed],FileExistsQ[$Failed],FileExistsQ[$Failed]}
 
@Jacccy Wow, your are not kidding me, right?
So, FileNames does find your files but they are non-existent.. hmm
 
I know it is weird....
 
@Jacccy Are you files by any chance on a network drive?
 
yes in GoogleDrive
 
1:37 PM
But Drive files are mirrored to your local drive and I'm doing this all the time.
 
usually I never had problem with this either
 
@Jacccy And you can open the file with an editor, yes?
So they are physically there?
 
yes, just tried this moment
 
OK, let us try something else.
Copy the full path of your Drive directory and the subdirectory where you files are located.
Something like
 
I remember a question where Importin an XLS didn't work if the file's path contained non-ASCII characters. Importing other some other filetypes worked.
Also this:
11
Q: How to workaround failures with Unicode filepaths?

Alexey Popkov(Cross-posted on the Wolfram Community.) The Mathematica's Kernel and FrontEnd currently work well with Unicode file/directory paths, but some other components of the system contain long-standing bugs which are source of troubles for the users, especially for the users from non-English-speaking ...

 
1:41 PM
dir = "C:\\Users\\..\\Google Drive\\your directory";
@Szabolcs Since Jacccy posted her path (which contains her name), I'm not sure she has Umlauts in the path.
@Jacccy Then try
files = FileNames[__~~"_0s"~~__~~".txt", {dir}]
Do you get the list of files too?
 
I didn't see the absolute path ...
At some point the relative path may get normalized.
See response in main room, it seems the absolute path may contain non-ASCII chars
@Jacccy I would test if Importing from a path without such characters is possible
 
@Jacccy Then you might try the solution of the post that @Szabolcs provided.
 
E.g. C:\\myTestDirectory\\...
Just in case.
I've seen some really weird bugs with RunProcess (that affected MaTeX) so at this point I wouldn't be surprised about anything.
 
This is so much information...I am working my way through...one minute
Here my directory where the *.nb files is saved

C:\Users\deichjkr\Google Drive\Raman\Ergebnisse\20180307_Methionin\Ergebnisse\20180622_Steffen_Jacqueline_Metbehandelt_Plasma\Auswertung
Here are my files located

C:\Users\deichjkr\Google Drive\Raman\Ergebnisse\20180307_Methionin\Ergebnisse\20180627_Steffen_Jacqueline_Metbehandelt_Plasma_Tag2\20180627_Txt_Files
 
1:57 PM
@Jacccy Hmm, but this path doesn't contain any weird characters. Can you use the last directory and find your files with
files = FileNames[__~~"_0s"~~__~~".txt", {dir}]
 
I tried, it is empty
{}
So I did
dir="C:\\Users\\deichjkr\\Google Drive\\Raman\\Ergebnisse\\20180307_Methionin\\Ergebnisse\\20180622_Steffen_Jacqueline_Metbehandelt_Plasma\\Auswertung"
files=FileNames[__~~"_0s"~~__~~".txt",{dir}]

Output: {}
 
@Jacccy I might have got the pattern wrong. What about
files = FileNames["*.txt", {dir}, Infinity]
Does this give some files?
 
ahhh now he found them all
 
And what give FileExistsQ /@ files now? Still false?
 
Wait, I checked the files....they are the wrong ones...they are not the ones lying two folders above the folder where I saved the *.nb file....
We need to find the ones from 20180627...
 
2:01 PM
@Jacccy Still, do these files exist for Mathematica?
 
This is now...
{True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
True, True, True, True, True, True, True, True, True, True, True, \
But we are working with the wrong files...
 
OK, that's a start. Now use this as dir
C:\Users\deichjkr\Google Drive\Raman\Ergebnisse\20180307_Methionin\Ergebnisse\20180627_Steffen_Jacqueline_Metbehandelt_Plasma_Tag2\20180627_Txt_Files
 
It was my mistake...I took the path from the *.nb file...
I already did...
he can find them know via
files = FileNames[__ ~~ "_0s" ~~ __ ~~ ".txt", {dir}]

He finds the right ones from 20180627
 
And do they exist with FileExistsQ?
 
yes
 
2:04 PM
Now use Import.
 
I which way?

Import["???","Table",HeaderLines->2]
 
@Jacccy For a start, do a simple Import[files[[1]],"Table",HeaderLines->2]
If this works, you can go ahead and use
 
Yes there they are =)
 
Import[#, "Table",HeaderLines->2]& /@ files
to import all files at once.
 
nice
 
2:09 PM
@Jacccy So what is our conclusion? The relative path brings somehow a bug to daylight.
 
as summary, I absolutely do not understand why mathematica has a problem with the import now, in other older files it worked completely fine
 
@Jacccy It seems specific to Windows. I never experienced such a behavior on OSX or Linux. At least you know now how we debugged it in case you run again in a similar issue.
 
I appriciate your time and curiousity very much!!!
I thank you!!!
 
@Jacccy No problem. That's what fellow German researchers are for. Have fun.
 

last day (14 days later) »