Hi,
The later specializations which were migrated from slack/forums to discourse followed the forum/slack like structure of having week by week categories (hence the parent - specialization → child → course, grandchild → week categorization which you see in most of them)
While we thought of migrating DLS,MLEP, and PDS as well, they already had too many posts and it became a big tedious task to take them to the same structure hence we kept them as is.
As for the new specializations and courses they follow the week category structure.
Learners and everyone is specifically not allowed to post as a topic in parent/child (specialization/course) category because that again causes problems as people don’t post in the right week categorization. I know it’s too much compartmentalization but this was the decision taken by the combined team managing discourse for a forum like specific category post for easy segmentation. If there are more complaints then maybe we can remove the restrictions.
For example, this post in MLEP is posted in the main specialization category and not a course (and it also became a headache of mentors/staff to put it in the right category or keep asking the learner where this question belongs)
If you want to post specific to the course or specialization, we do have introductions, resources and announcments which we can use. I think a feedback category per specialization would help with generic feedback if anyone wants to give or random discussion (just like slack had random channel). If that makes sense, maybe then it can done.
Also tagging @Community-Team/@Deepthi here as I might not have the right information after this month (as this is my last month here) so they will be your go-to people for discourse admin and other stuff
Thanks for the detailed response, @agparth, but I have some followup questions. If I’m correctly understanding how things are supposed to work according to the scheme you described, then the post that ai_curiousoriginally pointed out should never have been able to be created, right? It was created at the top parent level of AIM and thus doesn’t work correctly. Was it created before the structure was fully in place and rules enforced? But that can’t be it, since the OP of that thread is only 4 days old. So how did that happen? Should it be moved or is that also too much of a hassle? Or should I be talking to @Deepthi about this?
Actually now that I think about it the AIM mentors should be able to move threads, so you could delegate this cleanup work. I can move DLS threads by using the “edit pencil” on the title to change the categories, but I don’t see an edit pencil for the title in that AIM Thread. But I do see the wrench icon and it looks like I could close the thread. Hmmmm. In general I find that Discourse works really well, but the permissions and roles features seem a bit challenging to manage.
Update: actually I just read your post again and maybe I read too much into it the first time. I thought you were saying that people don’t have permission to create threads other than in the week forums. But maybe all you were saying that’s what you want/intend people to do and there is no enforcement mechanism. If that’s the case, then “good luck with that”. It is clearly explained somewhere, right? Or you can just do as I suggested earlier and dump it on the AIM mentors to clean up whatever messes get created. That’s how it works in DLS …
Yes. I just checked that thread and also checked the permissions and for people who joined with the AI4M link (from the course ) are put in learner group and the setting was accidentally set at learners being able to post in the main category. I have locked it now
Ideally, it should be moved to the correct course and week and there needs to be a sanity check across all categories and permissions once a while to catch this.
But maybe all you were saying that’s what you want/intend people to do and there is no enforcement mechanism. If that’s the case, then “good luck with that”. It is clearly explained somewhere, right? Or you can just do as I suggested earlier and dump it on the AIM mentors to clean up whatever messes get created. That’s how it works in DLS …
Yeah, there isn’t a mention of this, ideally, this is mentioned in the discourse etiquettes but it is not mentioned specifically. https://community.deeplearning.ai/faq
It is clearly explained somewhere, right? Or you can just do as I suggested earlier and dump it on the AIM mentors to clean up whatever messes get created. That’s how it works in DLS …
Can any one help me with an error in supervised learning week 3 assignment. The error is showing related to the code which is ineditable. Please help
Compute and display gradient with w and b initialized to zeros
initial_w = np.zeros(n)
initial_b = 0.
dj_db, dj_dw = compute_gradient(X_train, y_train, initial_w, initial_b)
print(f’dj_db at initial w and b (zeros):{dj_db}’ )
print(f’dj_dw at initial w and b (zeros):{dj_dw.tolist()}’ )
The above code is there given and cannot be edited in the assignment but has a programing error
ameError Traceback (most recent call last)
in
1 # Compute and display gradient with w and b initialized to zeros
----> 2 initial_w = np.zeros(n)
3 initial_b = 0.
4
5 dj_db, dj_dw = compute_gradient(X_train, y_train, initial_w, initial_b)
The code you cannot edit is part of the notebook. It does not have any errors. It is there to either set up the programming environment, or to test the code you have written.
The ‘n’ value is created when you run this cell from earlier in the notebook.
Tip:
Every time you open the notebook, you must run all of the cells starting from the top of the page. This is where the assets are imported and the workspace is configured.
It is clearly explained somewhere, right? Or you can just do as I suggested earlier and dump it on the AIM mentors to clean up whatever messes get created. That’s how it works in DLS 
…
It is clearly explained somewhere, right? Or you can just do as I suggested earlier and dump it on the AIM mentors to clean up whatever messes get created. That’s how it works in DLS 
…